Re: Ambiguous behaviour of age(timestamp) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Ambiguous behaviour of age(timestamp)
Date
Msg-id 18340.1101931276@sss.pgh.pa.us
Whole thread Raw
In response to Ambiguous behaviour of age(timestamp)  ("Kouber Saparev" <kouber@saparev.com>)
List pgsql-bugs
"Kouber Saparev" <kouber@saparev.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

pgsql-bugs by date:

Previous
From: postgresbugs
Date:
Subject: Foreign keys referencing parent table fails on insert
Next
From: Bruce Momjian
Date:
Subject: Re: Beta4 postgres.exe crash "...terminated by signal 5"