Possible age() bug?

From: "Mitch Vincent" <mitch(at)venux(dot)net>
To: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Possible age() bug?
Date: 2000-10-10 21:13:42
Message-ID: 01f501c032fe$f7f2f270$0200000a@doot
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Maybe I'm just overlooking something really simple but this has me a bit
confused.

What I'm trying to do is get the amount of time from A to B -- I thought
age() would do just that but it seems to be about a day off sometimes.

hhs=# SELECT age('Sun Dec 03 08:00:00 2000 EST','Tue Oct 10 08:00:00 2000
EDT') as esec;
esec
------------------------
@ 1 mon 24 days 1 hour
(1 row)

Ok, but if I turn right around and add that value back , I get :

hhs=# SELECT ('Tue Oct 10 08:00:00 2000 EDT'::timestamp + '1 mon 24 days 1
hour'::interval);
?column?
------------------------------
Mon Dec 04 08:00:00 2000 EST
(1 row)

Like I said, perhaps I'm blind and can't see what's happening here but
shouldn't that be Sunday the 3rd of December?

I should point out that it works as I expected it to on other values..

hhs=# SELECT age('Sun Nov 05 08:00:00 2000 EST','Tue Oct 10 08:00:00 2000
EDT') as esec;
esec
------------------
@ 26 days 1 hour
(1 row)

hhs=# SELECT ('Tue Oct 10 08:00:00 2000 EDT'::timestamp + '1 mon 24 days 1
hour'::interval);
?column?
------------------------------
Mon Dec 04 08:00:00 2000 EST
(1 row)

*shrug*

Thanks!

-Mitch

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mitch Vincent 2000-10-10 21:23:08 Re: Possible age() bug?
Previous Message Tom Lane 2000-10-10 21:10:53 Re: Re: [HACKERS] My new job