MIME-Version: 1.0
References: 
 <CAHGQGwGTyHgtD9tyN664x6vQ8Q1G53H7ZUCgBU9_X=nLt3f1QA@mail.gmail.com>
 <CALj2ACX_SSJYKt5od1C2874yeotTO9JewfRY9B=3DYx2daUAMw@mail.gmail.com>
 <CAHGQGwHTuLKTmW5DHtx-5yMuEq4=fc7M+UuvdOVekyvfsi=48Q@mail.gmail.com>
In-Reply-To: 
 <CAHGQGwHTuLKTmW5DHtx-5yMuEq4=fc7M+UuvdOVekyvfsi=48Q@mail.gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Date: Tue, 24 Mar 2026 20:09:48 -0700
Message-ID: 
 <CALj2ACUWnD=tg7ow+tx4zogSaJg=zr1_7KJwpU3h3MbaMyL0-w@mail.gmail.com>
Subject: Re: Reduce log level of some logical decoding messages to DEBUG1
To: Fujii Masao <masao.fujii@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CALj2ACUWnD%3Dtg7ow%2Btx4zogSaJg%3Dzr1_7KJwpU3h3MbaMyL0-w%40mail.gmail.com>
Precedence: bulk

Hi,

On Mon, Mar 23, 2026 at 8:44=E2=80=AFAM Fujii Masao <masao.fujii@gmail.com>=
 wrote:
>
> > I understand the chattiness of these when the decoding is done using
> > functions. But they seem to be useful when decoding using walsender
> > and replication connection. Also, it looks to me that the errdetail
> > describing various cases like when there are no running transactions,
> > when logical decoding will begin using saved snapshot, etc., is
> > helpful.
>
> I agree those messages are useful for developers. Do you think they're al=
so
> useful for DBAs, and therefore should remain at LOG level?
>
> > - 1 for another GUC IMHO. How about we find if the logical decoding is
> > being done using walsender (a boolean like isDecodingUsingWalSender,
> > default being false, set to true when in walsender) and emit them at
> > LOG level when set to true. Would something like this work?
>
> If we want to see those messages when walsender is performing logical
> decoding, that should still be possible even if we lower the level to DEB=
UG1.
> With the recent extension to log_min_messages (commit 38e0190ced7),
> we can enable them just for walsender
> (e.g., log_min_messages =3D 'warning,walsender:debug1').

I agree with this. One could use the new log_min_messages feature
introduced in PG19 if wanted. Perhaps, it's a good idea to add this
recommendation to the commit message to help those wanting to enable
these logs.

I reviewed the v1 patch and it LGTM. Thanks!

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com