Re: broken table formatting in psql - Mailing list pgsql-hackers

From John Naylor
Subject Re: broken table formatting in psql
Date
Msg-id CAFBsxsHnOhaTLGZFS-xoWRh-CngGjp9J5+B_LSV3Lrkh0a13fg@mail.gmail.com
Whole thread Raw
In response to Re: broken table formatting in psql  (John Naylor <john.naylor@enterprisedb.com>)
List pgsql-hackers
On Thu, Sep 8, 2022 at 12:39 PM John Naylor
<john.naylor@enterprisedb.com> wrote:
>
> On Fri, Sep 2, 2022 at 3:19 PM Kyotaro Horiguchi
> <horikyota.ntt@gmail.com> wrote:
> >
> > At Fri, 2 Sep 2022 13:43:50 +0700, John Naylor <john.naylor@enterprisedb.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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Splitting up guc.c
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: possibility to read dumped table's name from file