| From: | Jean-Paul Argudo <jean-paul(at)argudo(dot)org> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)ar> |
| Subject: | Re: age() vs. timestamp substraction |
| Date: | 2006-10-06 09:35:30 |
| Message-ID: | 45262362.4030101@argudo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Hi all,
> Where did you get that idea? age's reference point is current_date (ie,
> midnight) not now(). There are also some differences in the calculation
> compared to a plain timestamp subtraction.
I'm jumping on this thread to point out a little strange thing to me.
CURRENT_DATE, converted (stupidly) as a string *with* hour is "current
date at mid-day":
test=# select to_char(current_date,'YYYY-MM-DD HH:MI:SS');
to_char
---------------------
2006-10-06 12:00:00
(1 ligne)
It was a day when I had to debug a strange behaviour in a customer's
(bad) code :-)
Cheers,
--
Jean-Paul Argudo
www.PostgreSQLFr.org
www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2006-10-06 13:56:51 | Re: age() vs. timestamp substraction |
| Previous Message | Jim Nasby | 2006-10-06 02:40:57 | Re: [HACKERS] timestamp subtraction (was Re: formatting intervals with to_char) |