| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: how to completely turn off statement error logging |
| Date: | 2024-05-13 14:26:09 |
| Message-ID: | 740639.1715610369@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zwettler Markus (OIZ) | 2024-05-13 15:00:04 | AW: [Extern] Re: how to completely turn off statement error logging |
| Previous Message | David Rowley | 2024-05-13 14:22:03 | Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions |