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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
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 18:50:37
Message-ID: 8873.1577991037@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2020-01-02 18:57:38 pgsql: Reorder two nbtree.h function prototypes.
Previous Message Tom Lane 2020-01-02 18:49:00 pgsql: Fix collation exposed for scalar function in FROM.