PostgreSQL bug(?) – logging with a minimum log level

logpostgresqlpostgresql-9.3

I am using the log_min_error_statement – Setting in the PostgreSQL configuration file, but the logger does not react on the setting, either if I turn it on, or off, or set it to another level, the logger logs every statement. Could this be a possible bug in PostgreSQL logging?

Best Answer

the logger logs every statement

Then that behavior comes from log_statement:

log_statement (enum)

Controls which SQL statements are logged. Valid values are none (off), ddl, mod, and all (all statements). ddl logs all data definition statements,

Related Solutions

Postgresql – Unable to disable SQL statement logging in PostgreSQL 9.1

There are a number of relevant settings missing in your list. Check the chapter "When to log" in the manual, in particular these settings:

log_min_messages (enum)
log_min_error_statement (enum)
log_min_duration_statement (integer) -- as @Jack already hinted in his comment.

Postgresql – Limiting PostgreSQL logging

Yes you can hide those messages in the log.

In the calling session, before running the INSERT statement, issue this statement:

SET log_min_messages TO log;

If you want to still see the ERROR: part, and hide only the STATEMENT: part, use another parameter:

SET log_min_error_statement TO log;

See docs.

Use only session parameters, your application must know which statements will be silenced. Technically, you could make the setting permanent (in postgresql.conf) but it's not a good idea. In some cases this will be a footgun.

Best Answer

Related Solutions

Postgresql – Unable to disable SQL statement logging in PostgreSQL 9.1

Postgresql – Limiting PostgreSQL logging

Related Question