WALInsertLock is heavily contended and likely always will be even if we apply some of the planned fixes.
Some callers of WALInsertLock are more important than others * Writing new Clog or Multixact pages (serialized by ClogControlLock) * For Hot Standby, writing SnapshotData (serialized by ProcArrayLock) In these cases it seems like we can skip straight to the front of the WALInsertLock queue without problem. Most other items cannot be safely reordered, possibly no other items. We already re-order the lock queues when we hold shared locks, so we know in principle it is OK to do so. This is an extension of that thought. Implementing this would do much to remove my objection to performance issues associated with simplifying the Hot Standby patch, as recently suggested by Heikki. Possible? If so, we can discuss implementation. No worries if not, but just a side thought that may be fruitful. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
