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

From Harry Hochheiser
Subject Re: Default Timestamp 'Now' bug with 7.4 on Panther.
Date
Msg-id 1A91AEA0-6096-11D8-BF7C-0003938AD324@nih.gov
Whole thread Raw
In response to Re: Default Timestamp 'Now' bug with 7.4 on Panther.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Ok, thanks. that's what i get for using a premade package, I guess.

-harry

On Feb 15, 2004, at 1:31 PM, Tom Lane wrote:

> 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: Pavel Stehule
Date:
Subject: Re: plpgsql - variable's names conflict with table field
Next
From: Chris Campbell
Date:
Subject: Crash when calling a pl/pgsql function with no row to pass as an argument