From: | Thomas Lockhart <thomas(at)fourpalms(dot)org> |
---|---|
To: | Konrad Gdowski <konrad(at)spox(dot)org> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: date function 'age' problem |
Date: | 2002-04-03 14:28:08 |
Message-ID: | 3CAB1178.FF43E022@fourpalms.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> osk=> select age('2001-03-29','2001-03-01');
> ---------------
> 27 days 23:00
> osk=> select age('2002-03-29','2002-03-01');
> -------
> 1 mon
> osk=> select version();
> PostgreSQL 7.1.3 on i686-pc-linux-gnu, compiled by GCC 2.95.4
...
> look at the difference betwen results of execution function 'age' for the
> same time interval in year 2001 and 2002. why there is '1 mon' when it
> should be '27 days'.
You may be calculating an interval across daylight savings time
boundaries, which may have been done without accounting for time zones
in the version you are running. I'm not able to reproduce the problem on
my 7.2 installation:
thomas=# set time zone 'pst8pdt';
SET VARIABLE
thomas=# select age('2001-03-29','2001-03-01');
---------
28 days
thomas=# select age('2002-03-29','2002-03-01');
---------
28 days
thomas=# select version();
-----------------------------------------------------------
PostgreSQL 7.2 on i686-pc-linux-gnu, compiled by GCC 2.96
May be time to upgrade...
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-bugs | 2002-04-03 17:47:27 | Bug #628: move works incorrectly on cursors using GiST indexes |
Previous Message | Pierre-Alexis Paquin | 2002-04-03 09:02:42 | Bugs report |