Re: Should we document how column DEFAULT expressions work? - Mailing list pgsql-hackers

From David Rowley
Subject Re: Should we document how column DEFAULT expressions work?
Date
Msg-id CAApHDvo4z0pU81cfVZTTqWk28oT3rgswtV2nKzSHwDQ=P5aZ=w@mail.gmail.com
Whole thread Raw
In response to Re: Should we document how column DEFAULT expressions work?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Should we document how column DEFAULT expressions work?
List pgsql-hackers
On Wed, 26 Jun 2024 at 17:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Do we want to do anything about
> nextval()?  I guess if you hold your head at the correct
> angle, that's also a magic-input-value issue, in the sense
> that the question is when does regclass input get resolved.

I think I'm not understanding what's special about that.  Aren't
'now'::timestamp and 'seq_name'::regclass are just casts that are
evaluated during parse time in transformExpr()?

David



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Should we document how column DEFAULT expressions work?
Next
From: Tom Lane
Date:
Subject: Re: Should we document how column DEFAULT expressions work?