From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: broken table formatting in psql |
Date: | 2022-09-13 09:22:58 |
Message-ID: | CAFBsxsHnOhaTLGZFS-xoWRh-CngGjp9J5+B_LSV3Lrkh0a13fg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 8, 2022 at 12:39 PM John Naylor
<john(dot)naylor(at)enterprisedb(dot)com> wrote:
>
> On Fri, Sep 2, 2022 at 3:19 PM Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> >
> > At Fri, 2 Sep 2022 13:43:50 +0700, John Naylor <john(dot)naylor(at)enterprisedb(dot)com> wrote in
> > > If there is any doubt about including all of Cf, we could also just
> > > add a branch in wchar.c to hard-code the 200B-200F range.
> >
> > If every way has defect to the similar extent, I think we will choose
> > to use authoritative data at least for the first step. We might want
> > to have additional filtering on it but it would be another issue,
> > maybe.
> >
> > Attached is the first cut of that. (The commit messages is not great,
> > though.)
>
> Okay, the patch looks good to me overall.
As discussed, I pushed to master only, with only one additional
comment in the perl script to describe Me/Mn/Cf.
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2022-09-13 09:25:18 | Re: pgsql: Fix perltidy breaking perlcritic |
Previous Message | Alvaro Herrera | 2022-09-13 09:10:00 | Re: Splitting up guc.c |