| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, George Woodring <george(dot)woodring(at)iglass(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SQL solution for my JDBC timezone issue |
| Date: | 2015-02-23 21:33:29 |
| Message-ID: | CADK3HH+uSP5pYcqs0WM7CaErS635qPo7kfAHxen6Uo1hNmV_8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
On 23 February 2015 at 16:31, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dave Cramer <pg(at)fastcrypt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-02-23 23:34:45 | Re: Row-level Security vs Application-level authz |
| Previous Message | Tom Lane | 2015-02-23 21:31:28 | Re: SQL solution for my JDBC timezone issue |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | George Woodring | 2015-02-24 14:25:29 | Re: SQL solution for my JDBC timezone issue |
| Previous Message | Tom Lane | 2015-02-23 21:31:28 | Re: SQL solution for my JDBC timezone issue |