"Simon Riggs" <[EMAIL PROTECTED]> writes:
> It seems possible to reduce overall WAL volume by roughly 25% on common
> workloads by optimising the way UPDATE statements generate WAL.

This seems a huge amount of work to optimize *one* benchmark.  If it
weren't so narrowly focused on the properties of a particular benchmark
(mostly UPDATE, mostly a few columns in wide tuples), I'd get more
excited.  The extra time spent holding exclusive lock on the page
doesn't sound attractive either ...

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to