Re: Report search_path value back to the client.
Jelte Fennema <me@jeltef.nl>
From: Jelte Fennema-Nio <me@jeltef.nl>
To: Tomas Vondra <tomas@vondra.me>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>,
Tom Lane <tgl@sss.pgh.pa.us>, Alexey Klyukin <alexk@hintbits.com>,
Alexander Kukushkin <cyberdemn@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-08-14T16:30:52Z
Lists: pgsql-hackers
On Wed, 14 Aug 2024 at 18:22, Tomas Vondra <tomas@vondra.me> wrote: > Here's the patch with a somewhat expanded / improved commit message. > Jelte, can you take a look there's no silly mistake? Looks good to me.
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