MIME-Version: 1.0
References: <396C3BEE-CD4D-450A-8D28-E708E9AA4075@gmail.com>
In-Reply-To: <396C3BEE-CD4D-450A-8D28-E708E9AA4075@gmail.com>
From: Fujii Masao <masao.fujii@gmail.com>
Date: Fri, 5 Jun 2026 23:28:44 +0900
Message-ID: 
 <CAHGQGwH8De4O1mBZRHWATngQOqCb+1p741DW1rBKgWu2wkfaLw@mail.gmail.com>
Subject: Re: Prevent remote libpq notices from being sent to clients
To: Chao Li <li.evan.chao@gmail.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>,
 vignesh C <vignesh21@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAHGQGwH8De4O1mBZRHWATngQOqCb%2B1p741DW1rBKgWu2wkfaLw%40mail.gmail.com>
Precedence: bulk

On Fri, Jun 5, 2026 at 6:32=E2=80=AFPM Chao Li <li.evan.chao@gmail.com> wro=
te:
> So remote messages should only be output to the server log, but currently=
 they can leak to the client if client_min_messages is set to log.

I'm not sure whether it's good idea to add this limitation.

I just thought that some users might find it useful to send log messages
containing remote messages to the client when needed. For example,
in the following case, at least for me it seems helpful to see the LOG
message including the remote message:

    =3D# SELECT * FROM dblink_exec(..., 'create table if not exists t(i int=
)');
    LOG:  received message via remote connection: NOTICE:  relation
"t" already exists, skipping

So I'd like to hear more opinions from others. If the consensus is that
remote messages should never be sent to the client, I'm fine with
adding the limitation.

Regards,

--=20
Fujii Masao