Re: Add explicit warnings about unsafe OAuth trace output for libpq

> On 19 Aug 2026, at 14:06, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:

>>> The documentation already mentions that this option is unsafe because
>>> it prints out the HTTP traffic as-is, including secrets, but the
>>> output itself lacks a warning about it.
>>>
>>> Because the output is long, users might not notice that copy-pasting
>>> it or saving it to disk will share sensitive information. To increase
>>> visibility, this patch adds a warning to both the beginning and the
>>> end of the output.

I think it's a good idea to include a warning in the output like this. Ideally
it's just repeating what the user already knew but in case someone
missed/skipped the docs it's a healthy reminder. Unless there are different
opinions I proose to go ahead with this one.

--
Daniel Gustafsson