Re: Report search_path value back to the client.

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Jelte Fennema-Nio <me(at)jeltef(dot)nl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexey Klyukin <alexk(at)hintbits(dot)com>, Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Report search_path value back to the client.
Date: 2024-08-14 16:22:37
Message-ID: 35202526-2981-41bd-8477-4b25a45ceef6@vondra.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
v20240814-0001-Mark-search_path-as-GUC_REPORT.patch text/x-patch 2.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2024-08-14 16:30:52 Re: Report search_path value back to the client.
Previous Message Paul Jungwirth 2024-08-14 15:46:44 Re: format_datum debugging function