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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
Date: 2026-04-07 03:54:41
Message-ID: CAHGQGwGdfn4UPF8TmDPF5CinbrtxyUCHyny_ZuXHwXgSPyb2-w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Apr 7, 2026 at 12:33 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> The other possibility is to use AmRegularBackendProcess() to decide
> the log_level in this case.

Yes, that makes sense.

(I replied the same idea before seeing this message, sorry for the duplication.)

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2026-04-07 04:19:40 pgsql: Fix injection point detach timing problem in TAP test for lock s
Previous Message Fujii Masao 2026-04-07 03:51:32 Re: pgsql: Reduce log level of some logical decoding messages from LOG to D

Browse pgsql-hackers by date

  From Date Subject
Next Message jie wang 2026-04-07 03:55:15 Re: Add errdetail() with PID and UID about source of termination signal
Previous Message Fujii Masao 2026-04-07 03:51:32 Re: pgsql: Reduce log level of some logical decoding messages from LOG to D