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

Josh Berkus <josh@agliodbs.com>

From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Date: 2013-03-11T17:48:01Z
Lists: pgsql-hackers
> Having said that, I'd still be inclined to try to set the remote's
> timezone GUC just so that error messages coming back from the remote
> don't reflect a randomly different timezone, which was the basic issue
> in the buildfarm failures we saw yesterday.  OTOH, there is no guarantee
> at all that the remote has the same timezone database we do, so it may
> not know the zone or may think it has different DST rules than we think;
> so it's not clear how far we can get with that.  Maybe we should just
> set the remote session's timezone to GMT always.

Yeah, that seems the safest choice.  What are the potential drawbacks,
if any?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


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.