Re: broken table formatting in psql
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: John Naylor <john.naylor@enterprisedb.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-09-12T09:30:02Z
Lists: pgsql-hackers
po 12. 9. 2022 v 10:29 odesílatel John Naylor <john.naylor@enterprisedb.com> napsal: > On Mon, Sep 12, 2022 at 12:44 PM Pavel Stehule <pavel.stehule@gmail.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 >
Commits
-
Treat Unicode codepoints of category "Format" as non-spacing
- 0bd9c6297323 16.0 landed