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

From Tom Lane
Subject Re: WAL bypass for INSERT, UPDATE and DELETE?
Date
Msg-id 23765.1135271524@sss.pgh.pa.us
Whole thread Raw
In response to WAL bypass for INSERT, UPDATE and DELETE?  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: WAL bypass for INSERT, UPDATE and DELETE?
Re: WAL bypass for INSERT, UPDATE and DELETE?
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PL/pgSQL proposal: using list of scalars in assign stmts, fore and fors stmts
Next
From: "Jim C. Nasby"
Date:
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and DELETE?