From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com> |
Subject: | Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails |
Date: | 2021-09-26 08:56:57 |
Message-ID: | CAPmGK140mytM1nRdZZdsE+id57zJNcSiM=SOpwi4WPsCyWUT8A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Sat, Sep 25, 2021 at 10:59 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> writes:
> > On Sat, Sep 25, 2021 at 4:11 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?)
Yeah, I was thinking we could get it from a server option. Also, I
was thinking this bit might be back-patchable independently of the
solution mentioned above.
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2021-09-27 10:55:00 | Snapshot leak warning with lo_export in subtransaction |
Previous Message | Noah Misch | 2021-09-25 20:10:12 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |
From | Date | Subject | |
---|---|---|---|
Next Message | wangsh.fnst@fujitsu.com | 2021-09-26 08:57:55 | can we add some file(msvc) to gitignore |
Previous Message | wangsh.fnst@fujitsu.com | 2021-09-26 08:40:15 | RE: drop tablespace failed when location contains .. on win32 |