Re: WAL bypass for INSERT, UPDATE and DELETE?

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: bizgres-general <bizgres-general@pgfoundry.org>, pgsql-hackers@postgresql.org
Date: 2005-12-22T17:12:04Z
Lists: pgsql-hackers
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.

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.

			regards, tom lane