Skip site navigation (1) Skip section navigation (2)

Re: WAL bypass for INSERT, UPDATE and DELETE?

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: bizgres-general <bizgres-general(at)pgfoundry(dot)org>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: WAL bypass for INSERT, UPDATE and DELETE?
Date: 2005-12-22 20:10:54
Message-ID: 1135282254.2964.518.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, 2005-12-22 at 12:12 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-12-22 20:11:28
Subject: Re: Unsplitting btree index leaf pages
Previous:From: Jim C. NasbyDate: 2005-12-22 20:03:43
Subject: Re: Automatic function replanning

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group