From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Willy-Bas Loos <willybas(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: epoch and timezone changed bevior |
Date: | 2015-09-24 14:47:23 |
Message-ID: | 26631.1443106043@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Willy-Bas Loos <willybas(at)gmail(dot)com> writes:
> Is there a reason for this change of behavior between 8.4 and 9.* ?
See the "incompatibilities" section in the 9.2 release notes:
* Make EXTRACT(EPOCH FROM timestamp without time zone) measure the
epoch from local midnight, not UTC midnight (Tom Lane)
This change reverts an ill-considered change made in release
7.3. Measuring from UTC midnight was inconsistent because it made
the result dependent on the timezone setting, which computations
for timestamp without time zone should not be. The previous
behavior remains available by casting the input value to timestamp
with time zone.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-09-24 15:08:16 | Re: epoch and timezone changed bevior |
Previous Message | Adrian Klaver | 2015-09-24 14:40:11 | Re: epoch and timezone changed bevior |