| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(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-19 18:34:32 |
| Message-ID: | 4457e18c-784b-6009-5608-41d0fe3f683d@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/19/22 16:00, Robert Haas wrote:
> On Mon, Apr 18, 2022 at 3:39 PM Mark Dilger
> <mark(dot)dilger(at)enterprisedb(dot)com> wrote:
>> Since there hasn't been any agreement on that point, I've just rebased the patch to apply cleanly against the current master:
>
> This looks OK to me. There may be better ways to do some of it, but
> there's no rule against further improving the code later. Also, since
> the issue was introduced in v14, we probably shouldn't wait forever to
> do something about it. However, there is a procedural issue here now
> that we are past feature freeze. I think someone could defensibly take
> any of the following positions:
>
> (A) This is a new feature. Wait for v16.
> (B) This is a bug fix. Commit it now and back-patch to v14.
> (C) This is a cleanup that is OK to put into v15 even after feature
> freeze but since it is a behavior change we shouldn't back-patch it.
>
> I vote for (C). What do other people think?
I vote for (B).
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2022-04-19 19:07:35 | Re: Readd use of TAP subtests |
| Previous Message | Mark Wong | 2022-04-19 18:30:56 | Re: DBT-5 Stored Procedure Development (2022) |