| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Inconsistent behavior with AGE() |
| Date: | 2004-10-28 20:56:25 |
| Message-ID: | 200410281356.25970.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Folks,
Pardon me if this is redundant, but again the pgsql-bugs archives are not
working.
Summary: Various versions of AGE() give inconsistent results
Versions Tested: 7.4.2, 7.4.3, 8.0b4
Severity: Annoyance
Description: The age() built-in function sometimes truncates hours, minutes
and seconds, and sometimes it doesn't, depending on the parameters. This
seems inconsistent and confusing.
gforge=> select age('2004-01-01'::TIMESTAMP);
age
----------------
9 mons 27 days
(1 row)
gforge=> select age(now(),'2004-01-01'::TIMESTAMP);
age
------------------------------------
9 mons 27 days 11:17:19.8895479999
(1 row)
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-10-28 22:22:45 | Re: Inconsistent behavior with AGE() |
| Previous Message | PostgreSQL Bugs List | 2004-10-28 14:51:03 | BUG #1299: ordinal 2821 no en contrado en LIBEAY32.DLL |