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-17 07:05:26 |
Message-ID: | CAEyp7J87ATxN9HR3qKG5MftViXjGBKSwx7sGHic+ZumKRDh-pA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Dec 15, 2017 at 6:21 PM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> Venkata B Nagothi wrote:
> > > > 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 ?
>
> I don't understand - you'd have to explain what you mean.
>
> The setting doesn't change any data, it changes how a timestamp with time
> zone
> is displayed.
>
> It also sets the default time zone to use when a timestamp without timezone
> is to be converted to a timestamp with time zone, so maybe that's what you
> are observing.
>
My bad. It was my mis-understanding, the data did not change as it was
supposed to be. We had some bad data pushed from the application which led
to mis-understanding. All good now.
Regards,
Ven
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2017-12-17 18:20:23 | vacuum curiosity |
Previous Message | Corey Taylor | 2017-12-16 21:27:57 | Re: How to see index was rejected for seq scan? |