| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "SATYANARAYANA NARLAPURAM" <satyanarlapuram(at)gmail(dot)com>, "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logging replication state changes |
| Date: | 2022-01-09 02:55:44 |
| Message-ID: | a4886308-fab2-4073-b4c1-87a9185d4e4f@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
[1] https://wiki.postgresql.org/wiki/Todo
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2022-01-09 03:11:00 | Re: null iv parameter passed to combo_init() |
| Previous Message | Zhihong Yu | 2022-01-09 02:52:14 | Re: null iv parameter passed to combo_init() |