| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg14 psql broke \d datname.nspname.relname |
| Date: | 2021-10-13 16:46:27 |
| Message-ID: | CA+TgmoaH+nHJj1Y7poj2mE8Pa88qF_36QtXh5Mej_4ZJU=0fJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 12, 2021 at 12:57 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> I would prefer if it errored if the datname didn't match the current database.
> After all, it would've helped me to avoid making a confusing problem report.
How would you have felt if it had said something like:
error: argument to \d should be of the form
[schema-name-pattern.]relation-name-pattern
Would that have been better or worse for you than accepting a third
part of the pattern as a database name if and only if it matched the
current database name exactly?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-10-13 16:50:38 | Re: dfmgr additional ABI version fields |
| Previous Message | Hans Buschmann | 2021-10-13 16:44:53 | AW: VS2022: Support Visual Studio 2022 on Windows |