Re: Very strange 'now' behaviour in nested triggers. - Mailing list pgsql-sql

From Tom Lane
Subject Re: Very strange 'now' behaviour in nested triggers.
Date
Msg-id 9174.1059572934@sss.pgh.pa.us
Whole thread Raw
In response to Re: Very strange 'now' behaviour in nested triggers.  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-sql
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Strangely, CURRENT_TIMESTAMP converts to 'now', not now().  Is that a
> problem?

No, it is not, because the text-to-timestamptz conversion is marked
volatile and won't be const-folded.  I've always thought it was a very
ugly implementation though, mainly because it doesn't reverse-list
nicely in rule dumps.  Sometime we should try to fix it so that it
reverse-lists as "current_timestamp(n)", and likewise for the similar
special cases in gram.y.
        regards, tom lane


pgsql-sql by date:

Previous
From: Achilleus Mantzios
Date:
Subject: Re: How can I to solute this problem?
Next
From: Tom Lane
Date:
Subject: Re: now 7.2.3 - 7.3.3