Re: SQL solution for my JDBC timezone issue - Mailing list pgsql-general

From Dave Cramer
Subject Re: SQL solution for my JDBC timezone issue
Date
Msg-id CADK3HH+uSP5pYcqs0WM7CaErS635qPo7kfAHxen6Uo1hNmV_8w@mail.gmail.com
Whole thread Raw
In response to Re: SQL solution for my JDBC timezone issue  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general


On 23 February 2015 at 16:31, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Dave Cramer <pg@fastcrypt.com> writes:
> Everytime you get a connection the driver will issue set timezone ...
> It does not change the default time zone for the server (AFAICS)

Hmm ... depending on exactly how you issue it, it might become the default
for the session, I think.  I seem to recall that parameter settings
included in the startup packet become session-lifespan defaults.  If you
issued the SET as a separate command then a RESET ought to undo it.

That would explain it then as they are issued in the startup command

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: SQL solution for my JDBC timezone issue
Next
From: Stephen Frost
Date:
Subject: Re: Row-level Security vs Application-level authz