| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
| 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-25 13:59:33 |
| Message-ID: | 2501728.1632578373@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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?)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-25 14:59:27 | Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails |
| Previous Message | Etsuro Fujita | 2021-09-25 13:55:29 | Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-09-25 14:12:08 | Re: Fixing WAL instability in various TAP tests |
| Previous Message | Etsuro Fujita | 2021-09-25 13:55:29 | Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails |