Re: Excessive LOG messages from replication slot sync worker
От | Amit Kapila |
---|---|
Тема | Re: Excessive LOG messages from replication slot sync worker |
Дата | |
Msg-id | CAA4eK1+jaWqYOH43DxpwVp3yhwZa5JpSmT_Twxx2UZBzg9AHog@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Excessive LOG messages from replication slot sync worker (Fujii Masao <masao.fujii@gmail.com>) |
Ответы |
Re: Excessive LOG messages from replication slot sync worker
|
Список | pgsql-hackers |
On Tue, Aug 12, 2025 at 4:28 PM Fujii Masao <masao.fujii@gmail.com> wrote: > > I'm not sure these messages are useful for end users, and LOG might not be > the right level. They seem more like debug information, so should we consider > changing them to DEBUG, even with the proposed patch applied? > Yeah, we can do that for slotsync path but it should be okay to keep at LOG level for logical replication/decoding path as there it shouldn't hit as often as in slotsync path. But OTH, there is a argument that it can be DEBUG for logical replication/decoding path as well. From my experience, I can tell that these messages have been helpful in finding BF failures and debugging bugs from user reports, so there is value in keeping them at LOG level. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: