> On 10 May 2018, at 17:38, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> Well if you are using a timestamp with timezone field the value is always going to be stored as UTC. The TimeZone setting just determines the rotation from the input value to the stored value and the reverse. My previous point was just that Postgres will not enforce an offset on input data.
Good point.
>> Then the only way to know what the effective zone offset will be is to find out what the server default is.
>> Is this plausible?
>
> If you mean find the server default then yes:
>
> test_(aklaver)> select current_setting('TimeZone');
> current_setting
> -----------------
> US/Pacific
Thanks for the tip.