Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display
Date
Msg-id 202111161626.j2qn3mtxkvwa@alvherre.pgsql
Whole thread Raw
In response to Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display  ("Bossart, Nathan" <bossartn@amazon.com>)
Responses Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display
List pgsql-hackers
On 2021-Nov-16, Bossart, Nathan wrote:

> On 11/15/21, 7:14 PM, "Michael Paquier" <michael@paquier.xyz> wrote:
> > +       ereport(DEBUG1,
> > +                       (errmsg_internal("streaming %X/%X",
> > +                                                         LSN_FORMAT_ARGS(sentPtr))));
> > Anyway, those two ones are going to make the logs much more noisy, no?
> > The same could be said about XLogFileRead(), joining the point of
> > Nathan's upthread.  So I cannot get excited by this change.
> 
> Yeah, this might even be too noisy for DEBUG5.

Nod.  And if you're at DEBUG5, the log contains so much other crap that
it is unusable for any purposes anyway.

My opinion is that adding these things willy-nilly is not a solution to
any actual problem.  Adding a few additional log lines that are
low-volume at DEBUG1 might be useful, but below that (DEBUG2 etc) it's
not good for anything other than specific development, IMO.  At least
this particular one for streaming replication I think we should not
include.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Time to drop plpython2?
Next
From: Tom Lane
Date:
Subject: Re: Granting SET and ALTER SYSTE privileges for GUCs