| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(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 09:30:02 |
| Message-ID: | CAFj8pRBSTWEo5PbtxusfVsY=Vz3j2+Z3X0_-MJaVqY_mWGufgg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
po 12. 9. 2022 v 10:29 odesílatel John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
napsal:
> 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.
>
understand
Pavel
>
> --
> John Naylor
> EDB: http://www.enterprisedb.com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dagfinn Ilmari Mannsåker | 2022-09-12 09:54:47 | Re: pgsql: Fix perltidy breaking perlcritic |
| Previous Message | bt22kawamotok | 2022-09-12 09:20:30 | Re: [PATCH]Feature improvement for MERGE tab completion |