Re: Report search_path value back to the client.
Tom Lane <tgl@sss.pgh.pa.us>
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-19T17:57:59Z
Lists: pgsql-hackers
Tomas Vondra <tomas@vondra.me> writes: > On 8/19/24 18:19, Tom Lane wrote: >> 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. > Thanks, updated in a similar way. LGTM, thanks. regards, tom lane
Commits
-
Document that search_path is reported by the server
- 0d06a7eac4b2 18.0 landed
-
Mark search_path as GUC_REPORT
- 28a1121fd912 18.0 landed
-
Avoid spamming the client with multiple ParameterStatus messages.
- 2432b1a04087 14.0 cited
-
Mark application_name as GUC_REPORT so that the value will be reported back
- 59ed94ad0c9f 9.0.0 cited