Re: Logging replication state changes
От
Euler Taveira
Тема
Re: Logging replication state changes
Дата
Msg-id
a4886308-fab2-4073-b4c1-87a9185d4e4f@www.fastmail.com
Ответ на
Re: Logging replication state changes (SATYANARAYANA NARLAPURAM)
Список
Дерево обсуждения
Logging replication state changes SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
Re: Logging replication state changes Tom Lane <tgl@sss.pgh.pa.us>
Re: Logging replication state changes SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
Re: Logging replication state changes Amit Kapila <amit.kapila16@gmail.com>
Re: Logging replication state changes SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
Re: Logging replication state changes "Euler Taveira" <euler@eulerto.com>
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.
В списке pgsql-hackers по дате отправления
