Was this addressed?
> The "Integrated Document" on the web page has the following paragraph in
> the section "CREATE TABLE" in chapter 20.
>
> In the current release (v6.4), Postgres evaluates all default expressions at
> the time the table is defined. Hence, functions which are "non-cacheable"
> such as CURRENT_TIMESTAMP may not produce the desired effect. For the
> particular case of date/time types, one can work around this behavior by
> using "DEFAULT TEXT 'now'" instead of "DEFAULT 'now'" or "DEFAULT
> CURRENT_TIMESTAMP". This forces Postgres to consider the constant a string
> type and then to convert the value to timestamp at runtime.
>
> This appears to be untrue. Is this a change since 6.4 or is there
> some cases where using CURRENT_TIMESTAMP will not do the expected thing?
>
> Also, the title of the document (The PostgreSQL Development Team) seems
> to be incorrect.
>
> --
> D'Arcy J.M. Cain <darcy@{druid|vex}.net> | Democracy is three wolves
> http://www.druid.net/darcy/ | and a sheep voting on
> +1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
>
>
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026