From: DHS Webmaster <webmaster@dhs-club.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: bizarre AGE behaviour
Date: Wed, 03 Mar 2004 12:19:17 -0500
Message-ID: <40461395.5324CFEE@dhs-club.com> (raw)
Hello all,
Many thanks for this fine product.
We began encountering some unexpected date related errors this week and
after further investigation found the following. We use the postgres AGE
function in a custom function. The AGE function has begun to throw some
unanticipated results back. This has not happened before and my first
guess is that it may be leap year related. Here are some examples.
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.
--
Bill MacArthur
Webmaster
The DHS Club, Inc.
The Best Is Yet To Come!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: webmaster@dhs-club.com
Subject: Re: bizarre AGE behaviour
In-Reply-To: <40461395.5324CFEE@dhs-club.com>
References: <40461395.5324CFEE@dhs-club.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox