Re: pg14 psql broke \d datname.nspname.relname
От | Mark Dilger |
---|---|
Тема | Re: pg14 psql broke \d datname.nspname.relname |
Дата | |
Msg-id | 66BA0AF5-A3EB-4D3D-9B8F-B99AED22F27E@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: pg14 psql broke \d datname.nspname.relname (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
> On Oct 12, 2021, at 10:01 AM, Robert Haas <robertmhaas@gmail.com> wrote: > > On Tue, Oct 12, 2021 at 12:44 PM Peter Geoghegan <pg@bowt.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. I favor restoring the v13 behavior, but I don't think \d mydb.myschema.mytable was ever legitimate. You got exactly thesame results with \d nosuchdb.myschema.mytable, meaning the user was given a false sense of security that the databasename was being used to fetch the definition from the database they specified. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: