| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: pg14 psql broke \d datname.nspname.relname |
| Date: | 2022-04-08 03:04:44 |
| Message-ID: | 20220408030444.GH24419@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 07, 2022 at 10:26:18PM -0400, Robert Haas wrote:
> + pg_log_error("improper relation name (too many dotted names): %s", pattern);
>
> Come to think of it, maybe the error text there could stand some
> bikeshedding, but AFAICS
AFAICT the error text deliberately matches this, which I mentioned seems to me
the strongest argument for supporting \d datname.nspname.relname
ts=# SELECT 'a.a.a.a'::regclass;
ERROR: 42601: improper relation name (too many dotted names): a.a.a.a
LINE 1: SELECT 'a.a.a.a'::regclass;
^
LOCATION: makeRangeVarFromNameList, namespace.c:3129
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2022-04-08 03:39:47 | Re: pg14 psql broke \d datname.nspname.relname |
| Previous Message | Thomas Munro | 2022-04-08 02:56:15 | Re: Windows now has fdatasync() |