Re: Possible age() bug?

From: "Mitch Vincent" <mitch(at)venux(dot)net>
To: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Possible age() bug?
Date: 2000-10-10 21:23:08
Message-ID: 021701c03300$49b9bde0$0200000a@doot
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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)

I was obviously on drugs when I put this in the email, I apologize. It does
indeed work as I expected it to on other values.

In an old 6.4 database I get what I expected ::

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)

hhs=> SELECT ('Tue Oct 10 08:00:00 2000 EDT'::timestamp + '1 mon 24 days 1
hour'::interval);
?column?
----------------------------
Sun Dec 03 07:00:00 2000 CST
(1 row)

(Timezone differences are there and expected, these boxes are all across the
country).

-Mitch

In response to

Browse pgsql-hackers by date

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