Re: Report search_path value back to the client.

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jelte Fennema-Nio <me(at)jeltef(dot)nl>, 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-19 17:55:09
Message-ID: 556da1b5-fcd8-4edf-8e09-100b90c7b750@vondra.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/19/24 18:19, Tom Lane wrote:
> Tomas Vondra <tomas(at)vondra(dot)me> writes:
>> I see there are two places in libpq.sgml and protocol.sgml that should
>> list search_path - will fix. I haven't found any other place in the docs
>> that would need an update, or did I miss something?
>
> 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.

--
Tomas Vondra

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-08-19 17:57:59 Re: Report search_path value back to the client.
Previous Message Tom Lane 2024-08-19 17:52:07 Re: generic plans and "initial" pruning