| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg14 psql broke \d datname.nspname.relname |
| Date: | 2021-10-12 17:01:14 |
| Message-ID: | CA+Tgmob=3Y81s10EGYoyH7u1Hg88y=UajrH=Pu7pUnvYOsHVRQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 12, 2021 at 12:44 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> You're asking us to imagine a counterfactual. But this counterfactual
> bug report would have to describe a real practical problem.
Yes. And I think this one should be held to the same standard: \d
mydb.myschema.mytable not working is potentially a real, practical
problem. \d sdlgkjdss.dsgkjsk.sdgskldjgds.myschema.mytable not working
isn't.
> Let's assume that it is bug compatibility. Is that intrinsically a bad thing?
Well my view is that having the same bugs is better than having
different ones, but fixing the bugs is superior to either.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-10-12 17:03:29 | Re: pg14 psql broke \d datname.nspname.relname |
| Previous Message | Andres Freund | 2021-10-12 16:59:26 | Re: [RFC] building postgres with meson |