| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Japin Li <japinli(at)hotmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Excessive LOG messages from replication slot sync worker |
| Date: | 2025-08-13 04:00:23 |
| Message-ID: | CAA4eK1+jaWqYOH43DxpwVp3yhwZa5JpSmT_Twxx2UZBzg9AHog@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 12, 2025 at 4:28 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-08-13 04:14:14 | Re: Invalid remote sampling test in postgres_fdw. |
| Previous Message | Bertrand Drouvot | 2025-08-13 03:55:41 | Re: Adding locks statistics |