pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Etsuro Fujita <etsuro.fujita@gmail.com>
Cc: Ibrar Ahmed <ibrar.ahmad@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Neil Chen <carpenter.nail.cz@gmail.com>
Subject: Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails
Date: Sat, 25 Sep 2021 09:59:33 -0400
Message-ID: <2501728.1632578373@sss.pgh.pa.us> (raw)
In-Reply-To: <CAPmGK16g4qDfCqL7hAAdBpkCjz62gA1FSBpKtH=Bfnm6L=qkfA@mail.gmail.com>
References: <16583-4dc8f6c3b8ed24fa@postgresql.org>
	<422379.1612684550@sss.pgh.pa.us>
	<161476090989.29967.7097745522340560681.pgcf@coridan.postgresql.org>
	<CALtqXTdeSReq0Y1-mRAMO-SivqDRX_caamymdH9f=zsfLxsjow@mail.gmail.com>
	<3404441.1626208861@sss.pgh.pa.us>
	<CALtqXTdV2v5KmBNF1c_1uA=eYaLUZE7ecpxaNbLXo823=CEVzQ@mail.gmail.com>
	<CAPmGK15KFjpiHcu+fLVOJzH=41gTgTOqbbaUSwib1CKX0io69A@mail.gmail.com>
	<2201880.1630528969@sss.pgh.pa.us>
	<CAPmGK15ohpwdAPYA=Fw+C+DTdoPMWrpr6_q_XR6u3eJH7MSkVg@mail.gmail.com>
	<3683993.1631203221@sss.pgh.pa.us>
	<CAPmGK17wvbzpb6jsTEX7bK4JvoTqJK3M=MZx9xnVS=GhWs9_Ww@mail.gmail.com>
	<CAPmGK1759RxwEn2xH2nNqaK2LFOG1v9HkMMO4kpJAqrNfnho-Q@mail.gmail.com>
	<2438715.1632510693@sss.pgh.pa.us>
	<CAPmGK16g4qDfCqL7hAAdBpkCjz62gA1FSBpKtH=Bfnm6L=qkfA@mail.gmail.com>

Etsuro Fujita <etsuro.fujita@gmail.com> writes:
> On Sat, Sep 25, 2021 at 4:11 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Longer-term, it seems like we really have to be able to represent
>> the notion of a remote column that has an "unknown" collation (that
>> is, one that doesn't match any local collation, or at least is not
>> known to do so).

> +1

> In addition, a) we should detect whether local “default” matches
> remote “default”,

If we had a way to do that, most of the problem here wouldn't exist.
I don't believe we can do it reliably.  (Maybe we could put it on
the user to tell us, say via a foreign-server property?)

			regards, tom lane





view thread (28+ messages)  latest in thread

Message-ID: <2501728.1632578373@sss.pgh.pa.us>
Permalink:  ../2501728.1632578373@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2501728.1632578373@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, etsuro.fujita@gmail.com, ibrar.ahmad@gmail.com, pgsql-hackers@lists.postgresql.org, carpenter.nail.cz@gmail.com
  Subject: Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails
  In-Reply-To: <2501728.1632578373@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox