Horton

Re: Report search_path value back to the client.

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas@vondra.me>
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:19:07Z
Lists: pgsql-hackers 
Tomas Vondra <tomas@vondra.me> writes:
> 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?

I recall there being two places, so that's probably the extent of it
... yeah, the last similar patch was d16f8c8e4, and that's what
it did.

			regards, tom lane

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