| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Venkata B Nagothi <nag1010(at)gmail(dot)com> |
| 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 07:21:06 |
| Message-ID: | 1513322466.2504.3.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2017-12-15 09:59:20 | Re: User-defined print format for extension-defined types in psql output |
| Previous Message | John R Pierce | 2017-12-15 05:55:30 | Re: Can postgresql ignore DST ? |