Re: Default Timestamp 'Now' bug with 7.4 on Panther. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Default Timestamp 'Now' bug with 7.4 on Panther.
Date
Msg-id 9438.1076869892@sss.pgh.pa.us
Whole thread Raw
In response to Default Timestamp 'Now' bug with 7.4 on Panther.  (Harry Hochheiser <hsh@nih.gov>)
Responses Re: Default Timestamp 'Now' bug with 7.4 on Panther.  (Harry Hochheiser <hsh@nih.gov>)
List pgsql-bugs
Harry Hochheiser <hsh@nih.gov> writes:
> Running Postgres 7.4 on Panther, there seems to be a problem with
> setting a timestamp column to have a default of 'now':

There was an intentional change of behavior --- see the release notes.
The supported way to do this is to use CURRENT_TIMESTAMP or now() as
the column default.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: copy problem
Next
From: Pavel Stehule
Date:
Subject: plpgsql - variable's names conflict with table field names