| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-19 14:27:28 |
| Message-ID: | 20220419142728.GH26620@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 19, 2022 at 10:00:01AM -0400, Robert Haas wrote:
> (A) This is a new feature. Wait for v16.
> (B) This is a bug fix. Commit it now and back-patch to v14.
> (C) This is a cleanup that is OK to put into v15 even after feature
> freeze but since it is a behavior change we shouldn't back-patch it.
>
> I vote for (C). What do other people think?
I thought the plan was to backpatch to v14.
v14 psql had an unintentional behavior change, rejecting \d
datname.nspname.relname.
This patch is meant to relax that change by allowing datname, but only if it
matches the name of the current database ... without returning to the v13
behavior, which allowed arbitrary leading junk.
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2022-04-19 14:27:57 | Re: Add version and data directory to initdb output |
| Previous Message | Niyas Sait | 2022-04-19 14:22:30 | Re: [PATCH] Add native windows on arm64 support |