Comments (4)
Thanks!
In "advanced branch", a plurality of parameters were concatenated with spaces.
"refactored branch" is also, I think it is better to connect the spaces between the parameters.
Yeah, the current output is hard to identify each parameter. It should be fixed. I guess that using the space character as a separator make the it difficult to parse it by the analyser. Wouldn't it be better if we use a comma(,) character as a separator like follows?
LOG: AUDIT: SESSION,3,1,READ,2017-03-01 17:27:04 JST,postgres,postgres,[local],psql,2/3,0,,,SELECT,TABLE,pg_catalog.pg_extension,PREPARE prep_dx AS SELECT * FROM pg_extension WHERE extname = $1 AND extversion = $2;,,plpgsql,1.0
from pgaudit.
As a result of off-discussion, we use a space as separator for each parameters same as what advanced branch does.
Commit bf0df8d should fix it, please confirm it.
from pgaudit.
Thanks!
As with "advanced branch", it was confirmed that there was a space between the parameters.
LOG: connection received: host=[local]
LOG: connection authorized: user=postgres database=postgres
LOG: AUDIT: SESSION,1,1,MISC,2017-03-02 15:34:14 JST,postgres,postgres,[local],psql,2/27,0,,,BEGIN,,,BEGIN;,<none>
LOG: AUDIT: SESSION,2,1,READ,2017-03-02 15:34:14 JST,postgres,postgres,[local],psql,2/27,0,,,PREPARE,,,PREPARE prep_dx AS SELECT * FROM pg_extension WHERE extname = $1 AND extversion = $2;,<none>
LOG: AUDIT: SESSION,3,1,READ,2017-03-02 15:34:14 JST,postgres,postgres,[local],psql,2/27,0,,,SELECT,TABLE,pg_catalog.pg_extension,PREPARE prep_dx AS SELECT * FROM pg_extension WHERE extname = $1 AND extversion = $2;,plpgsql 1.0
LOG: AUDIT: SESSION,3,2,MISC,2017-03-02 15:34:14 JST,postgres,postgres,[local],psql,2/27,0,,,EXECUTE,,,"EXECUTE prep_dx ('plpgsql','1.0');",<none>
LOG: AUDIT: SESSION,4,1,READ,2017-03-02 15:34:14 JST,postgres,postgres,[local],psql,2/27,0,,,SELECT,TABLE,pg_catalog.pg_extension,PREPARE prep_dx AS SELECT * FROM pg_extension WHERE extname = $1 AND extversion = $2;,hogehoge 2.0
LOG: AUDIT: SESSION,4,2,MISC,2017-03-02 15:34:14 JST,postgres,postgres,[local],psql,2/27,0,,,EXECUTE,,,"EXECUTE prep_dx ('hogehoge','2.0');",<none>
LOG: AUDIT: SESSION,5,1,MISC,2017-03-02 15:34:14 JST,postgres,postgres,[local],psql,2/27,0,,,DEALLOCATE,,,DEALLOCATE PREPARE prep_dx;,<none>
LOG: AUDIT: SESSION,6,1,MISC,2017-03-02 15:34:14 JST,postgres,postgres,[local],psql,2/27,0,,,COMMIT,,,COMMIT;,<none>
LOG: disconnection: session time: 0:00:00.022 user=postgres database=postgres host=[local]
from pgaudit.
Thanks! Close.
from pgaudit.
Related Issues (20)
- (refactored branch) Defining multiple output sections does not cause an error. HOT 3
- (refactored branch) Setting file error does not occur even if the order of each section is changed. HOT 7
- (refactored branch) When log_connections or log_disconnections is turned off and reloaded, connection audit logs are no longer output. HOT 4
- (refactore branch) Update Copyright
- (refactored branch) Even if an unnecessary token exists in the setting file, it does not cause an error. HOT 3
- (refactored branche) Even if you specify WARNING as the level of the output section, the log level of the audit log is LOG instead of WARNING. HOT 3
- (refactored branche) Question: Does the parameter name in the setting file allow only lowercase letters? HOT 3
- (refactored branche) Parameters written in uppercase letters are ignored. HOT 3
- (refactored branch) There is a problem with the explanation of Session Audit Logging / Configuration of Readme.md. HOT 4
- (refactored branch) pid is not output to the audit log. HOT 5
- (refactored branch) The audit log that is output when pg_basebackup is executed is "class = SYSTEM" HOT 2
- (refactored branch) The filter by the database name has no effect on the audit log of the connection attempt. HOT 2
- (refactored branch) Even if you specify a command_tag filter, not filtered. HOT 2
- (refactored branch) Even if you specify a object_type filter, not filtered. HOT 3
- (refactored branch) Pattern matching with '%' character is not supported.
- (refactored branch) [bug] By config file description of mistakes, Segfault occurs during PostgreSQL start. HOT 3
- (refactored branch) Behavior when you specify an invalid timestamp literal HOT 4
- (refactored branch) Filters do not work correctly in the Japanese object name
- Rewriting README.md HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pgaudit.