Re: Reducing the log spam

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
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-02 11:11:44
Message-ID: CAGECzQRQx7X85tFa4cDWvXQMWTFyrvZw=vPttXv8S_9CUAfQXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hans Buschmann 2024-05-02 11:25:32 Type and CAST error on lowest negative integer values for smallint, int and bigint
Previous Message Jelte Fennema-Nio 2024-05-02 11:08:30 Re: Reducing the log spam