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

From Simon Riggs
Subject Re: COPY and Volatile default expressions
Date
Msg-id CA+U5nM+P_MMK7X4CqAszqdrgHLvAZpNK1dS9=yp2T6upn9E9qg@mail.gmail.com
Whole thread Raw
In response to Re: COPY and Volatile default expressions  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: COPY and Volatile default expressions
List pgsql-hackers
On 15 April 2013 21:53, Simon Riggs <simon@2ndquadrant.com> wrote:

> So I'll treat this as two separate cases:
> * add special case for sequences

Patch attached.

> * use the NO SQL mechanism, as described, which implies no reads or
> writes of database state. We could test that, but its somewhat harder
> and we'd need to test for that on entry to any function, which I don't
> much like.

For another time.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: "Colin 't Hart"
Date:
Subject: [PATCH] Add \ns command to psql
Next
From: Robert Haas
Date:
Subject: Re: event trigger API documentation?