Charles Seaton <[EMAIL PROTECTED]> writes:
> Thanks for your response. I am wondering whether it is postgres 8.2.5
> that resolves the problem or your time zone setting.
This behavior changed in PG 8.1. Per the release notes:
* Add a separate day field to type interval so a one day interval can
Niklas,
Thanks for your response. I am wondering whether it is postgres 8.2.5
that resolves the problem or your time zone setting.
I am running postgres 8.0.3. My server time zone is set to US/Pacific.
Setting my server time zone to one that does not have daylight saving
time causes the prob
On 3 nov 2007, at 12.26, Charles Seaton wrote:
select ('12/31/2006 UTC'::timestamptz + '307 days 02:45:30'::interval)
However, this gives an incorrect result (off by 1 hour)
"2007-11-02 18:45:30-07"
Have you checked your servers TimeZone setting? Also, which Postgres
version are you running?
Recently, in working with some data that was expressed as day of year +
time, I discovered an unexpected behavior in postgres's time handling. I
am wondering whether this is a bug or expected behavior that I simply
don't understand.
Given a day of year 307 and a time 04:45:30 UTC in 2007, an o
