Re: WAL bypass for INSERT, UPDATE and DELETE? - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: WAL bypass for INSERT, UPDATE and DELETE?
Date
Msg-id 1135282254.2964.518.camel@localhost.localdomain
Whole thread Raw
In response to Re: WAL bypass for INSERT, UPDATE and DELETE?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2005-12-22 at 12:12 -0500, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > Currently, CTAS optimization requires a heap_sync during ExecEndPlan. It
> > would be easy enough to extend this so that it also works for INSERT,
> > UPDATE and DELETE.
> 
> If you tried to do it that way you'd break the system completely.  Not
> all updates go through the executor.

Wow, didn't know that.

> I think it's a bad idea anyway; you'd be adding overhead to the lowest
> level routines in order to support a feature that would be very seldom
> used, at least in comparison to the number of times those routines are
> executed.

Agreed.

Maybe just INSERT SELECT then. That's easy enough to test for without
altering the main code path in the executor too much. If anybody is
going to say they want it?

Best Regards, Simon Riggs



pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Automatic function replanning
Next
From: Tom Lane
Date:
Subject: Re: Unsplitting btree index leaf pages