Re: Reducing the log spam

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reducing the log spam
Date: 2024-05-03 12:49:38
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, 2024-05-02 at 13:11 +0200, Jelte Fennema-Nio wrote:
> On Thu, 2 May 2024 at 13:08, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> > 2. Change the newly added check in errcode() to only set
> > output_to_server to false when IsLogicalWorker() returns false.
> Actually a third, and probably even better solution would be to only
> apply this new GUC to non-backgroundworker processes. That seems quite
> reasonable, since often the only way to access background worker
> errors is often through the logs.

That is a good idea. This version only suppresses error messages
in ordinary backend processes.

Laurenz Albe

Attachment Content-Type Size
v3-0001-Add-parameter-log_suppress_errcodes.patch text/x-patch 11.5 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Imseih (AWS), Sami 2024-05-03 12:57:18 Re: allow changing autovacuum_max_workers without restarting
Previous Message Peter Eisentraut 2024-05-03 12:27:40 Re: A failure in prepared_xacts test