public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Fujii Masao <[email protected]>
Cc: Chao Li <[email protected]>
Cc: Postgres hackers <[email protected]>
Cc: vignesh C <[email protected]>
Subject: Re: Prevent remote libpq notices from being sent to clients
Date: Fri, 05 Jun 2026 10:43:16 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHGQGwH8De4O1mBZRHWATngQOqCb+1p741DW1rBKgWu2wkfaLw@mail.gmail.com>
References: <[email protected]>
	<CAHGQGwH8De4O1mBZRHWATngQOqCb+1p741DW1rBKgWu2wkfaLw@mail.gmail.com>

Fujii Masao <[email protected]> writes:
> On Fri, Jun 5, 2026 at 6:32 PM Chao Li <[email protected]> wrote:
>> 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 was just about to answer saying that I didn't think so.  I'm
concerned that there might be no other way to obtain such output.
It's likely that the remote server doesn't log NOTICE-level messages,
and even if it does, you might not have access to its log.

Also, I don't buy the argument that this is a "leak": if the remote
server was willing to send the message to its client, it doesn't think
that the message is security-critical.

What I think there might be a good case for is to use the same ereport
level that was used to issue the remote's message, rather than always
LOG level.  I'm not sure if we can reconstruct that completely, but we
can certainly tell NOTICE from WARNING, for instance.

			regards, tom lane

view thread (6+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Prevent remote libpq notices from being sent to clients
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox