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>
 <CAHGQGwFB+hC97SHDpn1vOHHOq9uM5OZZmt50j7v6Z1JUNtH5zQ@mail.gmail.com>
In-Reply-To: 
 <CAHGQGwFB+hC97SHDpn1vOHHOq9uM5OZZmt50j7v6Z1JUNtH5zQ@mail.gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Date: Tue, 24 Mar 2026 20:28:23 -0700
Message-ID: 
 <CALj2ACXwe+iVoE50epmfGahYfoeBadgRr8ADvNHshWn0svv9hw@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/CALj2ACXwe%2BiVoE50epmfGahYfoeBadgRr8ADvNHshWn0svv9hw%40mail.gmail.com>
Precedence: bulk

Hi,

On Tue, Mar 24, 2026 at 8:15=E2=80=AFPM Fujii Masao <masao.fujii@gmail.com>=
 wrote:
>
> On Tue, Mar 24, 2026 at 12:44=E2=80=AFAM Fujii Masao <masao.fujii@gmail.c=
om> wrote:
> > > > Alternatively, if we want to keep them at LOG by default, we could =
introduce
> > > > a GUC like trace_logical_decoding_messages, similar to
> > > > the old trace_recovery_messages, to control their verbosity indepen=
dently
> > > > of log_min_messages.
>
> Just in case where many users still want to see those log messages at LOG=
 level,
> I also created a second patch (0002) that introduces a new GUC,
> trace_logical_decoding_messages, to control logging of logical
> decoding debug messages (e.g., "logical decoding found consistent point")=
.

-1 for another GUC. If needed, we could explore using
log_replication_commands, but I'm okay with your other suggestion on
using the new feature with log_min_messages. Perhaps, we could wait
for some time to hear from others.

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