Re: Reducing the log spam - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Reducing the log spam
Date
Msg-id f8c77c1a17150fa6a0eff997e81052b6c1215b77.camel@cybertec.at
Whole thread Raw
In response to Re: Reducing the log spam  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers
On Mon, 2024-03-11 at 09:33 +0100, Jelte Fennema-Nio wrote:
> -   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.

The actual SQLSTATEs that get suppressed are subject to discussion
(an I have a gut feeling that some people will want the list empty).

As far as this specific functionality is concerned, I think that the
actual problem is a deficiency in PostgreSQL.  The problem is that
the log is the *only* place where you can get this information.  That
will be a problem for many people, even without "log_suppress_errcodes".

I think that this isformation should be available in some statistics
view.

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Regardign RecentFlushPtr in WalSndWaitForWal()
Next
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: Using the %m printf format more