Horton
Menu

Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables)

Daniel Farina <daniel@heroku.com>

View thread
From: Daniel Farina <daniel@heroku.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2013-03-11T20:52:23Z
Lists: pgsql-hackers 
On Mon, Mar 11, 2013 at 12:30 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> BTW, it strikes me that dblink is probably subject to at least some of
> these same failure modes.  I'm not personally volunteering to fix any
> of this in dblink, but maybe someone ought to look into that.

I will try to make time for this, although it seems like the general
approach should match pgsql_fdw if possible.  Is the current thinking
to forward the settings and then use the GUC hooks to track updates?

--
fdr

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix postgres_fdw's issues with inconsistent interpretation of data values.