Re: IMPORT FOREIGN SCHEMA statement

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: David Fetter <david(at)fetter(dot)org>
Cc: Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: IMPORT FOREIGN SCHEMA statement
Date: 2014-05-27 13:52:27
Message-ID: 20140527135227.GH2556@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* David Fetter (david(at)fetter(dot)org) wrote:
> In the "easy" case of PostgreSQL, you might also be able to establish
> whether the UDT in the "already defined locally" case above is
> identical to the one defined remotely, but I don't think it's possible
> even in principle for non-PostgreSQL remote systems, possibly not even
> for ones with non-identical architecture, PostgreSQL major version,
> etc.

For my 2c, it'd be very handy if IMPORT had an option or similar to also
copy over all (in the schema) or at least any depended-upon UDTs. It'd
really be nice if we had an ability to check the remote UDT vs. the
local one at some point also, since otherwise you're going to get bitten
at run-time when querying the foreign table.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-05-27 13:52:46 Re: [PATCH] Replacement for OSSP-UUID for Linux and BSD
Previous Message Stephen Frost 2014-05-27 13:41:06 Re: IMPORT FOREIGN SCHEMA statement