Re: pg14 psql broke \d datname.nspname.relname

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>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg14 psql broke \d datname.nspname.relname
Date: 2021-10-13 17:05:58
Message-ID: CA+Tgmoa0GeR8O=q24CjrDKR3Z61Wszvh=kCeP0mCVR4QjZ3CFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 13, 2021 at 12:54 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> It seems unfortunate if names from log messages qualified with datname were now
> rejected. Like this one:
>
> | automatic analyze of table "ts.child.cdrs_2021_10_12"...

That's a good argument, IMHO.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-10-13 17:14:32 Re: prevent immature WAL streaming
Previous Message Justin Pryzby 2021-10-13 16:54:26 Re: pg14 psql broke \d datname.nspname.relname