| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: broken table formatting in psql |
| Date: | 2022-09-12 08:28:49 |
| Message-ID: | CAFBsxsGueu3Nceb98ScP1HcPTTg6Yfqy8LJ-37X0wHkRCyi8og@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 12, 2022 at 12:44 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> This is not a critical issue, really. On second thought, I don't see the point in releasing fresh Postgres with this bug, where there is know bugfix - and this bugfix should be compatible (at this moment) with 16.
I agree the actual logic/data change is low-risk. The patch renames
two files, which seems a bit much this late in the cycle. Maybe that's
okay, but I'd like someone else to opine before doing so.
--
John Naylor
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-09-12 08:40:47 | Re: pg_stat_statements locking |
| Previous Message | Peter Eisentraut | 2022-09-12 08:28:38 | Re: pg_walinspect float4/float8 confusion |