Andres Freund writes:
But I think that actually coordinating a consistent visibility order
between commit, wal insertion and the procarray would have bigger
scalability impact than the second record. I might be missing some
clever tricks here though.
Yeah. ISTM the only way to really guarantee that the visible commit
order is the same would be for transactions to hold the ProcArrayLock
while they're inserting that WAL record. Needless to say, that would
be absolutely disastrous performance-wise.

Or at least, that's true as long as we rely on the current procarray-based
mechanism for noting that a transaction is still in progress. Maybe
there's some other approach altogether.

    regards, tom lane

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 5 of 7 | next ›
Discussion Overview
grouppgsql-hackers @
categoriespostgresql
postedAug 28, '13 at 2:58p
activeAug 29, '13 at 10:24p
posts7
users4
websitepostgresql.org...
irc#postgresql

People

Translate

site design / logo © 2017 Grokbase