Horton

Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Etsuro Fujita <etsuro.fujita@gmail.com>
Cc: Ibrar Ahmed <ibrar.ahmad@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Neil Chen <carpenter.nail.cz@gmail.com>
Date: 2021-09-25T14:59:27Z
Lists: pgsql-bugs, pgsql-hackers 
Etsuro Fujita <etsuro.fujita@gmail.com> writes:
> On Sat, Sep 25, 2021 at 4:11 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> As a short-term answer, I propose that we apply (and back-patch) the
>> attached documentation changes.

> The attached patch looks good to me.

I've pushed that, and marked the current CF entry as returned with
feedback.  I'm not sure how soon I might get around to trying the
idea of an explicit "unknown" collation ... if anyone wants to take
a stab at that, feel free.

			regards, tom lane

Commits

  1. Doc: extend warnings about collation-mismatch hazards in postgres_fdw.

  2. Add support for asynchronous execution.

  3. Suppress unnecessary RelabelType nodes in yet more cases.