On Wed, Apr 1, 2026 at 2:44 AM Fujii Masao <[email protected]> wrote: > Reduce log level of some logical decoding messages from LOG to DEBUG1
Hi, Apologies for not having noticed this thread before the patch was committed, but I have some reservations about this change. I agree that if someone is calling pg_logical_slot_get_changes() regularly, it isn't good to write a LOG message every time. However, I am concerned that this may make problems with regular logical decoding much harder to debug. I see that there was some discussion of adding a GUC to raise the level back up to LOG, but I feel like that wouldn't help much. If something goes wrong, enabling the messages for the future won't tell you what went wrong in the past. I am wondering whether a better approach might be to set the LOG level based on context -- that is, if it's actually logical decoding, log this at LOG, but if it's just someone peeking at a slot or similar, reduce the log level to DEBUG1 or, really, probably more like DEBUG3. Thoughts? -- Robert Haas EDB: http://www.enterprisedb.com
