Re: pgsql-server/src backend/catalog/heap.c backen ... - Mailing list pgsql-committers

From Christopher Kings-Lynne
Subject Re: pgsql-server/src backend/catalog/heap.c backen ...
Date
Msg-id 08f501c3563c$5ddbac90$2800a8c0@mars
Whole thread Raw
In response to pgsql-server/src backend/catalog/heap.c backen ...  (tgl@svr1.postgresql.org (Tom Lane))
Responses Re: pgsql-server/src backend/catalog/heap.c backen ...
List pgsql-committers
> Log message:
> Coerce unknown-literal-constant default values to the column type during
> CREATE TABLE (or ALTER TABLE SET DEFAULT), rather than postponing it to
> the time that the default is inserted into an INSERT command by the
> rewriter.  This reverses an old decision that was intended to make the
> world safe for writing
> f1 timestamp default 'now'

Does that mean that default current_timestamp will work?

Chris


pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql-server/src/backend/access/nbtree Tag: RE ...
Next
From: Tom Lane
Date:
Subject: Re: pgsql-server/src backend/catalog/heap.c backen ...