From: | Venkata B Nagothi <nag1010(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Can postgresql ignore DST ? |
Date: | 2017-12-15 02:20:52 |
Message-ID: | CAEyp7J80UX2Tm=N=AnNKuhe_s9JqGRDT0EUTgbjaxNVOKcpd0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 14 Dec 2017 at 7:28 pm, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> Venkata B Nagothi wrote:
> > On Thu, 14 Dec 2017 at 4:04 pm, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > > Venkata B Nagothi <nag1010(at)gmail(dot)com> writes:
> > > > To rule out any application issues, is it possible to get postgresql
> to
> > > > ignore DST and render all the timestamps with timezone offsets of
> +11 ?
> > >
> > > set timezone = 11
> >
> > We have Timezone configured to Australia/Sydney, we can change that to
> 11 and do we need to foresee any issues ?
>
> That configuration parameter defines how the client will format
> timestamps to strings and vice versa.
>
> It should not have any other effects.
I think what I see is some dates might have changed - is that a possibility
?
If yes, is there any way I can revert back ?
Regards,
Ven
> --
Regards,
Venkata B N
Database Consultant
From | Date | Subject | |
---|---|---|---|
Next Message | TAKATSUKA Haruka | 2017-12-15 03:20:13 | Hot standby failing with PANIC: WAL contains references to invalid pages |
Previous Message | legrand legrand | 2017-12-14 23:08:32 | Re: Does the delete+insert is fater and less cpu consumer than update? |