> Von: Tom Lane <t...@sss.pgh.pa.us> > Gesendet: Montag, 13. Mai 2024 16:26 > An: Zwettler Markus (OIZ) <markus.zwett...@zuerich.ch> > Cc: pgsql-general@lists.postgresql.org > Betreff: [Extern] Re: how to completely turn off statement error logging > > "Zwettler Markus (OIZ)" <markus.zwett...@zuerich.ch> writes: > > I don't want to log statement errors in the server logfile - whether the > > statement > string nor the error message. > > You need to set log_min_messages higher than ERROR. You might consider > using LOG or FATAL rather than PANIC, though. > > > I set "log_min_error_statement = panic" according to the docs: > > To effectively turn off logging of failing statements, set this parameter to > PANIC. > > This setting controls whether the STATEMENT: detail is appended to a message, > but not the basic choice of whether to emit the message. > > regards, tom lane > --- Externe Email: Vorsicht mit Anhängen, Links oder dem Preisgeben von > Informationen ---
please let me refine. I would like to suppress all errors in the server logfile coming from client applications, i.e. statement level errors such as "duplicate key violates..." but I do not want to suppress errors that are related to infrastructure problems, i.e. "could not open file..." if I set log_min_messages higher than ERROR, errors concerning the infrastructure would also be suppressed, wouldn't they? thanks, markus
