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: Jelte Fennema-Nio <me@jeltef.nl>
Cc: 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-19T15:20:57Z
Lists: pgsql-hackers 
On 8/14/24 18:30, Jelte Fennema-Nio wrote:
> 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.

Pushed, after rewording the commit message a bit.

Now let's see how the other protocol thread goes ...


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