Re: pgsql: Make parser rely more heavily on the ParseNamespaceItem data str

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Make parser rely more heavily on the ParseNamespaceItem data str
Date: 2020-01-02 22:35:24
Message-ID: CAOBaU_ZBbqVpgv8QJ0LkMqUdTAFOGfqBZp5FkeUhbxxtdu2Suw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Jan 2, 2020 at 7:50 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> > On Thu, Jan 2, 2020 at 6:41 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Hmm, the buildfarm seems to think this screwed up something affecting
> >> collations. Looking ...
>
> > Is ORDER BY 1 COLLATE "C" an option here?
>
> Nah, that would just mask the bug not fix it. See 4d02eb017.

Ah indeed I see, thanks.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2020-01-03 00:45:12 pgsql: Minor portability fixes for new TAP script.
Previous Message Peter Geoghegan 2020-01-02 21:31:35 pgsql: Correct _bt_delitems_vacuum() lock comments.