Re: Default Timestamp 'Now' bug with 7.4 on Panther.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Harry Hochheiser <hsh(at)nih(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org, siah(at)nih(dot)gov
Subject: Re: Default Timestamp 'Now' bug with 7.4 on Panther.
Date: 2004-02-15 18:31:32
Message-ID: 9438.1076869892@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Harry Hochheiser <hsh(at)nih(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-02-15 18:41:50 Re: copy problem
Previous Message Tom Lane 2004-02-15 18:29:37 Re: Problem with datatype REAL using the = (EQUAL) operator