Re: Logging replication state changes - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: Logging replication state changes
Date
Msg-id a4886308-fab2-4073-b4c1-87a9185d4e4f@www.fastmail.com
Whole thread Raw
In response to Re: Logging replication state changes  (SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>)
List pgsql-hackers
On Sat, Jan 8, 2022, at 6:29 PM, SATYANARAYANA NARLAPURAM wrote:
We need the historical information to analyze and root cause in addition to the live debugging. It would be good to have better control over replication messages. 
I think the answer to this demand is not to change the message level but to
implement a per-module log_min_messages. This idea is in the TODO [1] for more
than a decade. Check the archives.

I agree with Tom that the referred messages are noisy, hence, DEBUG1 is fine
for it.



--
Euler Taveira

pgsql-hackers by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: null iv parameter passed to combo_init()
Next
From: Noah Misch
Date:
Subject: Re: null iv parameter passed to combo_init()