From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: postgres_fdw does not see enums |
Date: | 2014-12-03 22:41:59 |
Message-ID: | 20141203224159.GA11134@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 03, 2014 at 05:38:47PM -0500, Tom Lane wrote:
> David Fetter <david(at)fetter(dot)org> writes:
> > I've been trying out 9.5-to-be's PostgreSQL FDW, and I noticed
> > that it doesn't seem to handle enum types. Would this be a
> > trivial fix?
>
> No. How would you know whether the remote side even has the enum,
> let alone whether it has an identical set of members? I don't see
> that enums are noticeably easier than the general case of
> non-built-in types ...
I must be missing something important. When querying the remote side,
*and it's PostgreSQL*, we have catalog access that could be used to
reconstruct the enums. Or are you thinking about the case where the
enum changes from one call to the next?
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-12-03 22:52:03 | Re: postgres_fdw does not see enums |
Previous Message | Tom Lane | 2014-12-03 22:38:47 | Re: postgres_fdw does not see enums |