Horton
Menu

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Farina <daniel@heroku.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2013-03-12T18:51:17Z
Lists: pgsql-hackers 
Daniel Farina <daniel@heroku.com> writes:
> Okay, I see.  So inverting the thinking I wrote earlier: how about
> hearkening carefully to any ParameterStatus messages on the local side
> before entering the inner loop of dblink.c:materializeResult as to set
> the local GUC (and carefully dropping it back off after
> materializeResult) so that the the _in functions can evaluate the
> input in the same relevant GUC context as the remote side?

Yeah, watching the remote side's datestyle and intervalstyle and
matching them (for both input and output) would probably work.

			regards, tom lane

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.