| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: IMPORT FOREIGN SCHEMA statement |
| Date: | 2014-07-10 23:12:15 |
| Message-ID: | CAB7nPqR=s4sJ26ZRNTJEqM4etgZUp_sX=ELT00+nwiUxNMNR4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 11, 2014 at 4:06 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
> > So I propose we invent a couple more import options, say
> > import_default and import_collate, and make the postgres_fdw
> > code do the obvious thing with them. import_default should
> > probably default to false, but I'm about halfway tempted to
> > say that import_collate should default to true --- if you're
> > importing a collatable column and you don't have a matching
> > locale locally, it seems like it'd be better if we complain
> > about that by default.
>
> I've committed this patch with that addition and some minor additional
> cleanup.
>
Thanks!
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-07-11 00:17:59 | Re: Allowing NOT IN to use ANTI joins |
| Previous Message | David Fetter | 2014-07-10 22:46:43 | Re: Missing autocomplete for CREATE DATABASE |