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

From Bruce Momjian
Subject Re: COPY and Volatile default expressions
Date
Msg-id 20130416135817.GG5343@momjian.us
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 Tue, Apr 16, 2013 at 02:37:33PM +0100, Simon Riggs wrote:
> On 16 April 2013 13:57, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
> 
> > You still need to check the args, if the function is nextval, otherwise you
> > incorrectly perform the optimization for something like
> > "nextval(myvolatilefunc())".
> 
> Guess so. At least its an easy change.

I found Simon's nextval()/COPY timings without this patch sobering.  I
assume he can apply this for 9.3, right?  I believe it is a fix for a
new 9.3 feature.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: COPY and Volatile default expressions
Next
From: Simon Riggs
Date:
Subject: Re: Enabling Checksums