Re: bizarre AGE behaviour

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: DHS Webmaster <webmaster(at)dhs-club(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: bizarre AGE behaviour
Date: 2004-03-03 18:00:05
Message-ID: 200403031000.05524.scrawford@pinpointresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wednesday 03 March 2004 9:19 am, DHS Webmaster wrote:
> We began encountering some unexpected date related errors this
week...
<snip>
> This is good...
> network=# select age('04-01-04','03-01-04');
> age
> -------
> 1 mon
> (1 row)
>
> This isn't...
> network=# select age('05-01-04','03-01-04');
> age
> ---------------------
> 1 mon 30 days 23:00
> (1 row)
>
> Now it gets really strange......
> network=# select age('06-01-04','04-01-04');
> age
> ---------------------
> 1 mon 29 days 23:00
> (1 row)
>
> This may have been addressed in the past (I subscribe to this list)
> and I just missed it, but is there a simple fix for this problem?
> Thanks.

It was originally addressed long in the past (1784, Paris by Benjamin
Franklin): http://webexhibits.org/daylightsaving/

US Daylight Saving Time starts this year on April 4 when 0200 jumps to
0300. The answers PostgreSQL gave are correct.

Cheers,
Steve

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2004-03-03 23:19:19 Re: bizarre AGE behaviour
Previous Message DHS Webmaster 2004-03-03 17:19:17 bizarre AGE behaviour