Re: pgsql: Collations with nondeterministic comparison

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(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: Collations with nondeterministic comparison
Date: 2019-03-25 07:17:28
Message-ID: d5342eaa-bdaf-b515-7f16-6464dbfb530a@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 2019-03-25 06:07, Tom Lane wrote:
> Buildfarm member snapper doesn't like this. I think the problem is
> that the queries it's failing on do not bother to constrain their
> output row order. Adding an "EXPLAIN" right there indicates that
> the INTERSECTs are being done via hashing, meaning that platform
> specific output ordering is to be expected. I don't have a
> big-endian platform with ICU installed, but if I did I bet I could
> replicate the failure on it.

pushed a fix

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2019-03-25 07:20:55 pgsql: tableam: Add and use table_fetch_row_version().
Previous Message Peter Eisentraut 2019-03-25 07:16:35 pgsql: Add ORDER BY to regression test case