| From: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "Robert Haas *EXTERN*" <robertmhaas(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql_fdw, FDW for PostgreSQL server |
| Date: | 2011-12-07 07:34:45 |
| Message-ID: | CAEZqfEcON-R+9NYxCFf6tHeOVLKydQQha9BS+nWJpYGgo9HcBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sorry for delayed response.
2011/11/29 Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>:
> I think that this is not always safe even from PostgreSQL to PostgreSQL.
> If two databases have different collation, "<" on strings will behave
> differently.
Indeed. I think that only the owner of foreign table can keep collation
consistent between foreign and local, like data type of column. We need to
support per-column-collation on foreign tables too, or should deny pushing
down condition which is collation-sensitive...
Regards,--
Shigeru Hanada
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-12-07 07:40:33 | Re: Timing overhead and Linux clock sources |
| Previous Message | Pavel Stehule | 2011-12-07 07:23:32 | Re: review: CHECK FUNCTION statement |