| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: postgres_fdw IMPORT SCHEMA and partitioned tables |
| Date: | 2017-03-31 19:32:33 |
| Message-ID: | CA+TgmobjK4F7Nd5cM=6ygCnC0g8Do=RP7pTWsUJZYe5SxbzXhA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 31, 2017 at 3:31 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> Committed after rewording the documentation.
>
> Hm. Wonder if something like that shouldn't be backpatched - because
> otherwise using postgres_fdw from an old server against a newer one will
> do weird stuff. I don't know what kind of policy we've committed to
> with postgresImportForeignSchema...
I don't think I'd like to promise that postgres_fdw will always be
forward-compatible. Backward-compatibility is hard enough already.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-31 19:34:57 | Re: Allow to specify #columns in heap/index_form_tuple |
| Previous Message | Andres Freund | 2017-03-31 19:31:35 | Re: postgres_fdw IMPORT SCHEMA and partitioned tables |