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-03-11 08:33:48
Message-ID: CAGECzQRMBMN+WozaGEBt3b7JCC65MFk5H3uRprQ-YdErM0+qhg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

- the subscriber's server log.
+ the subscriber's server log if you remove <literal>23505</literal> from
+ <xref linkend="guc-log-suppress-errcodes"/>.

This seems like a pretty big regression. Being able to know why your
replication got closed seems pretty critical.

On Mon, 11 Mar 2024 at 03:44, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Sat, 2024-03-09 at 14:03 +0100, Laurenz Albe wrote:
> > Here is a patch that implements this.
>
> And here is patch v2 that fixes a bug and passes the regression tests.
>
> Yours,
> Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Svetlana Derevyanko 2024-03-11 08:38:40 Re: Add Index-level REINDEX with multiple jobs
Previous Message Anthonin Bonnefoy 2024-03-11 08:23:16 Fix expecteddir argument in pg_regress