Re: [BUGS] Seems bug in postgres_fdw?

On Mon, Feb 27, 2017 at 10:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Sachin Kotwal <kotsachin(at)gmail(dot)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
>
>
>
Tom -

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?

Thanks
-Dave