From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Varying results when using merge joins over postgres_fdw vs hash joins |
Date: | 2017-09-20 16:35:34 |
Message-ID: | 7098.1505925334@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> I would like postgres_fdw to be taught about collation versioning, so
> that postgres_fdw's IMPORT could automatically do the right thing when
> ICU is in use. Maybe it's too early to discuss that, because we don't
> even support alternative collation provider collations as the
> database/cluster default collation just yet. FWIW, postgres_fdw +
> collations was one of the issues that made me believe in the long term
> strategic importance of ICU.
TBH, the more I learn about ICU, the less faith I have in the proposition
that it's going to fix anything at all for us in this area. It seems to
be just about as squishy as glibc in terms of locale identification,
if not worse.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-09-20 16:42:05 | Re: Varying results when using merge joins over postgres_fdw vs hash joins |
Previous Message | Tom Lane | 2017-09-20 16:28:02 | Re: Varying results when using merge joins over postgres_fdw vs hash joins |