Re: Fix unqualified catalog references in psql describe queries

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: "Bertrand Drouvot" <bertranddrouvot(dot)pg(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Michael Paquier" <michael(at)paquier(dot)xyz>, "Chao Li" <li(dot)evan(dot)chao(at)gmail(dot)com>, "L(dot) pgsql-hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>, "Peter Eisentraut" <peter(at)eisentraut(dot)org>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, "Ashutosh Bapat" <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: Fix unqualified catalog references in psql describe queries
Date: 2026-06-10 08:33:35
Message-ID: b4baf3aa-c93a-4e70-bec4-41f20a117904@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-06-10, Bertrand Drouvot wrote:

> I do agree that doing so would "destroy" the readability. I did not
> look in detail,
> but what about forcing ALWAYS_SECURE_SEARCH_PATH_SQL before the queries
> and
> restore the search_path once the query is done? (that way that would
> not impact
> the readability)

I think we should just ditch the idea that operators live in schemas.

--
Álvaro Herrera

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jakub Wartak 2026-06-10 08:33:36 Re: repack: clarify final phase of concurrent mode in file header comment
Previous Message Amit Langote 2026-06-10 08:32:27 Re: PG19 FK fast path: OOB write and missed FK checks during batched