> On Mar 15, 2022, at 12:27 PM, Robert Haas <robertmh...@gmail.com> wrote: > > - Justin Pryzby, who originally discovered the problem, prefers the > same behavior that I prefer long-term, but thinks Tom's behavior is > better than doing nothing. > - Mark Dilger, Isaac Moreland, Garick Hamlin, Alvaro Herrera, and > Julien Rouhaud have commented on the thread but have not endorsed > either of these dueling proposals. I vote in favor of committing the patch, though I'd also say it's not super important to me. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
- Re: pg14 psql broke \d datname.nspname.relname Robert Haas
- Re: pg14 psql broke \d datname.nspname.relname Mark Dilger
- Re: pg14 psql broke \d datname.nspname.relname David G. Johnston
- Re: pg14 psql broke \d datname.nspname.relname Justin Pryzby
- Re: pg14 psql broke \d datname.nspname.relname Andres Freund
- Re: pg14 psql broke \d datname.nspname.relname Mark Dilger
- Re: pg14 psql broke \d datname.nspname.reln... Robert Haas
- Re: pg14 psql broke \d datname.nspname.... Mark Dilger
- Re: pg14 psql broke \d datname.nsp... Robert Haas
- Re: pg14 psql broke \d datname... Mark Dilger
- Re: pg14 psql broke \d dat... Robert Haas
- Re: pg14 psql broke \d dat... Tom Lane