pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: postgres_fdw IMPORT SCHEMA and partitioned tables
Date: Fri, 31 Mar 2017 15:55:30 -0400
Message-ID: <15973.1490990130@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+TgmobjK4F7Nd5cM=6ygCnC0g8Do=RP7pTWsUJZYe5SxbzXhA@mail.gmail.com>
References: <20170309141531.GD9812@tamriel.snowman.net>
	<CAB7nPqSjyMBDDk+RHRoPVZ7yWZTvq73_Bg0HTG9hR0T=O1f5mg@mail.gmail.com>
	<eeebe90d-523f-9b0b-be46-8b5f34ea5412@lab.ntt.co.jp>
	<CA+TgmobwR1WjV19Wv1GtZoBSXVHX9HpwSfSdjZtnPNhH0SgxMQ@mail.gmail.com>
	<CAB7nPqTDpzym=vJz-LooFHfdO-5fudb=b5XacEXHWVCZeULMjw@mail.gmail.com>
	<CAB7nPqSh=8dd=gDrcS_ASecG_et8t2VmgSuPyHf57e2=mpWi+A@mail.gmail.com>
	<2cab6db2-cf10-b8f2-58ed-7d4a052dac34@lab.ntt.co.jp>
	<CAB7nPqSj1xWbkOYt+Cob3S_xYYxam1rN0_bvRVnb0HHMV5iZeg@mail.gmail.com>
	<15303833-838d-079c-2fa2-c01e93771387@lab.ntt.co.jp>
	<CA+TgmoZd9WQG63oCWHX07kWtqQtsmihR+MiWyYuioNiH2v3-Ew@mail.gmail.com>
	<20170331193135.wwg5pqsrc634p3dg@alap3.anarazel.de>
	<CA+TgmobjK4F7Nd5cM=6ygCnC0g8Do=RP7pTWsUJZYe5SxbzXhA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Mar 31, 2017 at 3:31 PM, Andres Freund <andres@anarazel.de> wrote:
>> 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.

Unless I'm missing something, the behavior will be that an older
version will simply ignore remote partitioned tables (they will not
pass the relkind filter in the query).  Seems pretty fail-soft,
so I think it's fine.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (14+ messages)  latest in thread

Message-ID: <15973.1490990130@sss.pgh.pa.us>
Permalink:  ../15973.1490990130@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15973.1490990130@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, andres@anarazel.de, Langote_Amit_f8@lab.ntt.co.jp, michael.paquier@gmail.com, sfrost@snowman.net
  Subject: Re: postgres_fdw IMPORT SCHEMA and partitioned tables
  In-Reply-To: <15973.1490990130@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox