Re: Fix unqualified catalog references in psql describe queries
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: Álvaro Herrera <alvherre@kurilemu.de>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, Michael Paquier
<michael@paquier.xyz>, Chao Li <li.evan.chao@gmail.com>, "L. pgsql-hackers"
<pgsql-hackers@lists.postgresql.org>, Fujii Masao <masao.fujii@gmail.com>,
Peter Eisentraut <peter@eisentraut.org>, Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>
Date: 2026-07-08T00:04:48Z
Lists: pgsql-hackers
On Mon, 2026-06-15 at 23:21 +0200, Álvaro Herrera wrote: > I am imagining that only database owners would be able to create > operators. There isn't any case for allowing that for anybody else, > ISTM. How much need is there for "less-trusted" operators, really? That's probably true in almost all cases. Operators are generally defined as part of an extension that offers interesting types and opclasses, and these are C extensions anyway. I haven't ever seen someone define a convenience operator like they might define a convenience function. Perhaps some use it for some clever hacks around unmodifiable application code or something? Regards, Jeff Davis
Commits
-
psql: Add some missing schema qualifications in describe.c
- bf5206f00773 19 (unreleased) landed
-
SQL Property Graph Queries (SQL/PGQ)
- 2f094e7ac691 19 (unreleased) cited
-
CREATE SUBSCRIPTION ... SERVER.
- 8185bb534763 19 (unreleased) cited