| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: \dP and \dX use ::regclass without "pg_catalog." |
| Date: | 2022-01-08 20:03:39 |
| Message-ID: | 1581830.1641672219@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> My point is that it's good to have it, but it would be much better to
> have something bulletproof, which we could use in an automated check
> somewhere (next to stuff like perlcritic, perhaps). I don't know what,
> though.
Meh ... this is mostly cosmetic these days, so I can't get excited
about putting a lot of work into it. We disclaimed search path
bulletproofness for all these queries a long time ago.
I don't object to fixing it in the name of consistency, but that's
not a reason to invest large effort.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2022-01-08 21:29:24 | Re: warn if GUC set to an invalid shared library |
| Previous Message | Andrey Lepikhov | 2022-01-08 20:02:23 | Multiple Query IDs for a rewritten parse tree |