Re: WAL bypass for INSERT, UPDATE and DELETE?
| От | Tom Lane |
|---|---|
| Тема | Re: WAL bypass for INSERT, UPDATE and DELETE? |
| Дата | |
| Msg-id | 23765.1135271524@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | WAL bypass for INSERT, UPDATE and DELETE? (Simon Riggs <simon@2ndquadrant.com>) |
| Ответы |
Re: WAL bypass for INSERT, UPDATE and DELETE?
Re: WAL bypass for INSERT, UPDATE and DELETE? |
| Список | 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 по дате отправления: