| From: | George Woodring <george(dot)woodring(at)iglass(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SQL solution for my JDBC timezone issue |
| Date: | 2015-02-23 20:15:57 |
| Message-ID: | CACi+J=Sp1yFe-GsGO2Cxp3G1w7X38hkEeLdKk381AHuqYPeuSA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
This is what I was looking for, however the JDBC does something to make its
timezone the default.
My cluster is set to GMT, I have a DB that is set to US/Pacific, when I
get the connection from JDBC it is US/Eastern. The reset command does not
affect it. I can set timezone in the code to 'US/Pacific" and I see it
change, when I do another RESET timezone it goes back to US/Eastern.
Thanks,
George Woodring
iGLASS Networks
www.iglass.net
On Mon, Feb 23, 2015 at 10:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> George Woodring <george(dot)woodring(at)iglass(dot)net> writes:
> > Yes, that is where we think we are heading, the issue is that the code
> does
> > not know what it needs to be set back to. We have 90 databases with 5
> > different time zones. I was just hoping for a more elegant solution than
> > writing a lookup table that says if you are connecting to db x then set
> to
> > timezone y.
>
> "RESET timezone" ?
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-02-23 20:29:28 | Re: SQL solution for my JDBC timezone issue |
| Previous Message | Adrian Klaver | 2015-02-23 19:46:23 | Re: Sequences not moved to new tablespace |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-02-23 20:29:28 | Re: SQL solution for my JDBC timezone issue |
| Previous Message | Dave Cramer | 2015-02-23 16:57:47 | Re: [GENERAL] SQL solution for my JDBC timezone issue |