Skip site navigation (1) Skip section navigation (2)

Re: Ambiguous behaviour of age(timestamp)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kouber Saparev" <kouber(at)saparev(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Ambiguous behaviour of age(timestamp)
Date: 2004-12-01 20:01:16
Message-ID: 18340.1101931276@sss.pgh.pa.us (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-bugs
"Kouber Saparev" <kouber(at)saparev(dot)com> writes:
> I think the documentation is misleading, because AGE(timestamp) is actually
> converted to AGE(current_date, timestamp), and not to AGE(now(), timestamp).

Well, it says "Subtract from today", which I'd interpret as meaning
"current_date" not "now", but I made it say "Subtract from current_date"
just to be sure.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Dave PageDate: 2004-12-01 20:27:18
Subject: Re: BUG #1319: Windows LIB file libecpg.lib not in build or package
Previous:From: postgresbugsDate: 2004-12-01 19:58:46
Subject: Foreign keys referencing parent table fails on insert

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group