| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Collations with nondeterministic comparison |
| Date: | 2019-03-26 17:13:02 |
| Message-ID: | CAH2-WzmTN3ggT5TK+nevJb_zM-Jz-xVaF906T4BeOT+8T1B=yw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Mon, Mar 25, 2019 at 12:17 AM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> 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
Buildfarm member snapper is still unhappy about this:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snapper&dt=2019-03-26%2013%3A01%3A31
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-26 17:19:14 | Re: pgsql: Get rid of backtracking in jsonpath_scan.l |
| Previous Message | Andrew Dunstan | 2019-03-26 17:11:14 | Re: pgsql: Get rid of backtracking in jsonpath_scan.l |