From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Peter Geoghegan <pg(at)bowt(dot)ie> |
Subject: | Re: pg14 psql broke \d datname.nspname.relname |
Date: | 2022-04-18 19:39:17 |
Message-ID: | CEB5C11E-D731-4EE7-B076-03D0CB7DAA03@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Apr 8, 2022, at 4:11 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> I don't personally see how we're going to come out ahead with that
> approach, but if you or Tom or someone else want to put something
> together, that's fine with me. I'm not stuck on this approach, I just
> don't see how we come out ahead with the type of thing you're talking
> about. I mean we could return the error text, but it's only to a
> handful of places, so it just doesn't really seem like a win over what
> the patch is already doing.
Since there hasn't been any agreement on that point, I've just rebased the patch to apply cleanly against the current master:
Attachment | Content-Type | Size |
---|---|---|
v9-0001-Reject-patterns-with-too-many-parts-or-wrong-db.patch | application/octet-stream | 78.0 KB |
unknown_filename | text/plain | 96 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-18 19:41:37 | Re: Why does pg_class.reltuples count only live tuples in indexes (after VACUUM runs)? |
Previous Message | Andrew Dunstan | 2022-04-18 19:29:18 | Re: Postgres perl module namespace |