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: Tomas Vondra <tomas.vondra@enterprisedb.com>, 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-14T16:22:37Z
Lists: pgsql-hackers

Attachments

Here's the patch with a somewhat expanded / improved commit message.
Jelte, can you take a look there's no silly mistake?

As mentioned previously, I plan to push this, so that if the protocol
improvements from [1] don't land in PG18 we have at least something. I
did take a brief look at the other thread, but it's hard to predict.

[1]
https://www.postgresql.org/message-id/CAGECzQTg2hcmb5GaU53uuWcdC7gCNJFLL6mnW0WNhWHgq9UTgw%40mail.gmail.com

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