Horton

Re: Report search_path value back to the client.

Tomas Vondra <tomas@vondra.me>

View thread View on postgr.es
From: Tomas Vondra <tomas@vondra.me>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jelte Fennema-Nio <me@jeltef.nl>, Alexey Klyukin <alexk@hintbits.com>, Alexander Kukushkin <cyberdemn@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-08-19T16:10:58Z
Lists: pgsql-hackers 
On 8/19/24 18:02, Tom Lane wrote:
> Tomas Vondra <tomas@vondra.me> writes:
>> On 8/14/24 18:30, Jelte Fennema-Nio wrote:
>>> Looks good to me.
> 
>> Pushed, after rewording the commit message a bit.
> 
> This patch does not appear to have updated any of the relevant
> documentation.
> 

Oh, I haven't realized we explicitly list which parameters are reported.

I see there are two places in libpq.sgml and protocol.sgml that should
list search_path - will fix. I haven't found any other place in the docs
that would need an update, or did I miss something?


regards

-- 
Tomas Vondra

Commits

  1. Document that search_path is reported by the server

  2. Mark search_path as GUC_REPORT

  3. Avoid spamming the client with multiple ParameterStatus messages.

  4. Mark application_name as GUC_REPORT so that the value will be reported back