On Wed, Mar 14, 2012 at 3:29 PM, Jeff Janes <jeff.ja...@gmail.com> wrote: > I think my analysis is pretty much a re-wording of yours, but I'd > emphasize that getting the WALWriteLock is bad not just because they > fight over the lock, but because someone else (probably background wal > writer) is camping out on the lock while doing an fsync.
Yeah, good point. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
