Re: COPY and Volatile default expressions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: COPY and Volatile default expressions
Date
Msg-id CA+TgmoYunLHaD66QX2J58YQmj58RFuOMDzp-a_guMzfbbPP3=A@mail.gmail.com
Whole thread Raw
In response to Re: COPY and Volatile default expressions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: COPY and Volatile default expressions
Re: COPY and Volatile default expressions
List pgsql-hackers
On Mon, Apr 15, 2013 at 11:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I claim this is a common class, since sequence next_val functions and
>> uuid generators meet that criteria and most common forms of auditing
>> trigger, as well as any other form of data-reformatting trigger.
>
> I don't believe that it's a good idea to consider nextval() to be
> reorderable, so I'm not convinced by your argument here.

Why not?

I admit that I can't convince myself that it's safe.  But I can't
think of a concrete example where it breaks anything, either.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: COPY and Volatile default expressions
Next
From: Rodrigo Barboza
Date:
Subject: Query not using index for user defined type