Horton
Menu

Re: pgsql: Reduce log level of some logical decoding messages from LOG to D

Amit Kapila <amit.kapila16@gmail.com>

View thread
From: Amit Kapila <amit.kapila16@gmail.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-10T09:54:55Z
Lists: pgsql-hackers 
On Tue, Apr 7, 2026 at 11:39 AM Fujii Masao <masao.fujii@gmail.com> wrote:
>
> On Tue, Apr 7, 2026 at 12:54 PM Fujii Masao <masao.fujii@gmail.com> wrote:
> >
> > On Tue, Apr 7, 2026 at 12:33 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> > > The other possibility is to use AmRegularBackendProcess() to decide
> > > the log_level in this case.
> >
> > Yes, that makes sense.
>
> I've updated the patch to use AmRegularBackendProcess(). Patch attached.
>

LGTM.

-- 
With Regards,
Amit Kapila.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Adjust log level of logical decoding messages by context

  2. Reduce log level of some logical decoding messages from LOG to DEBUG1