On Sat, Sep 25, 2021 at 10:59 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > Etsuro Fujita <etsuro.fuj...@gmail.com> writes: > > On Sat, Sep 25, 2021 at 4:11 AM Tom Lane <t...@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?)
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
