| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| 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:31:28 |
| Message-ID: | 12783.1424727088@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2015-02-23 21:33:29 | Re: SQL solution for my JDBC timezone issue |
| Previous Message | Luca Ferrari | 2015-02-23 20:36:36 | Re: 9.3.5 failing to compile with dtrace on FreeBSD 10.1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2015-02-23 21:33:29 | Re: SQL solution for my JDBC timezone issue |
| Previous Message | Dave Cramer | 2015-02-23 20:32:31 | Re: SQL solution for my JDBC timezone issue |