Thread: Re: [HACKERS] [BUGS] Seems bug in postgres_fdw?

Sachin Kotwal <kotsachin@gmail.com> writes:
> Here , Why postgresql takes different time when remote table and foreign
> table have different definition for timestamp column?

I believe postgres_fdw sets the timezone in its remote session to UTC
for predictability of results.  Your table definition is really at fault
for being dependent on what the session timezone is.

Personally I'd make the ins_ts column be timestamp with time zone, but
if you really don't want to do that, you could consider making the default
expression be "current_timestamp AT TIME ZONE 'something'" to force the
rotated value to be in a particular zone.

                        regards, tom lane

On Thu, Mar 2, 2017 at 3:28 AM, Rader, David <davidr@openscg.com> wrote:
> Attached is a doc patch that updates the documentation for postgres-fdw to
> include the actual values for the 4 session variables that are set. Does
> that make sense to clarify?

From my point of view, this would be a sensible thing to document,
although I feel like the grammar is not quite right, because after
"establishes remote session settings for the parameters" my brain
expects a list of parameters rather than a list of parameters and the
corresponding values.  I think it reads better if you change "for the
parameters" to "for various parameters".

</nitpicking>