Re: literature on write-ahead logging - Mailing list pgsql-hackers

From Tom Lane
Subject Re: literature on write-ahead logging
Date
Msg-id 10192.1307638375@sss.pgh.pa.us
Whole thread Raw
In response to literature on write-ahead logging  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: literature on write-ahead logging
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> [ lots of interesting stuff about WAL optimization snipped ]

> ... Second, they aren't really using locks, unless you count
> bus locks - they appear to have implemented most or all of it via
> CAS-based lock-free algorithms, which is probably well-justified
> optimization effort.

FWIW, I'm pretty suspicious of claims that lock-free data structures
will be some kind of magic bullet.  As far as I can tell, a very large
part of our contention problems on many-core machines stem from the CPUs
fighting over cache line ownership.  Avoiding an explicit lock in favor
of hardware primitive test-and-modify instructions isn't going to do a
darn thing to improve that.  And contorting the algorithms until they
fit into what's portably available in that line could easily be a net
loss.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: tuning autovacuum
Next
From: Kohei KaiGai
Date:
Subject: Re: [v9.1] sepgsql - userspace access vector cache