| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(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 14:37:06 |
| Message-ID: | 4919.1405003026@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com> writes:
> Similarly to what we do for the schema, we should also check that the server
> in the parsed statement is the one we are importing from.
Hm. The FDW would really have to go out of its way to put the wrong thing
there, so is this worth the trouble? It's not like the creation schema
where you can easily omit it from the command; the syntax requires it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-07-10 14:46:30 | Re: Pg_upgrade and toast tables bug discovered |
| Previous Message | Tom Lane | 2014-07-10 14:26:33 | Re: IMPORT FOREIGN SCHEMA statement |