From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Can postgresql ignore DST ? |
Date: | 2017-12-15 05:55:30 |
Message-ID: | c7596dea-48d6-ff4a-2582-aa292b5ac1a6@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/14/2017 9:17 PM, Venkata B Nagothi wrote:
>
> On Fri, Dec 15, 2017 at 3:23 PM, Ben Madin <ben(at)ausvet(dot)com(dot)au
> <mailto:ben(at)ausvet(dot)com(dot)au>> wrote:
>
> I'd be a little worried that if you set timezone = 11 for
> Australia/Sydney you are embedding the daylight savings value, not
> the standard time value (UTC+10)
>
>
> Totally agree. We have a weird situation where-in i had to do this and
> i would like to learn the impact on the data, i hope it would not
> fiddle the existing data. We are currently experimenting this.
in PostgreSQL, fields that are type TIMESTAMP WITH TIME ZONE convert all
input time values to UTC, and store it in an internal representation,
and on output, they are converted to the client's current TIMEZONE.
--
john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2017-12-15 07:21:06 | Re: Can postgresql ignore DST ? |
Previous Message | Venkata B Nagothi | 2017-12-15 05:17:39 | Re: Can postgresql ignore DST ? |