I wrote:
> ... enabling LWLOCK_STATS shows that the contention
> rate on the sinval locks is now completely negligible --- one block
> per thousand acquisitions on SInvalWriteLock, and less than one in
> 1 on SInvalReadLock. The vast majority of the LWLock contention
> now comes from WALInsert
I wrote:
> In this thread back in January
> http://archives.postgresql.org/pgsql-performance/2008-01/msg1.php
> we saw evidence that contention for SInvalLock was a problem,
> and we (or at least I) concluded that the sinval messaging system
> needed a nontrivial rewrite to get rid of its habit
In this thread back in January
http://archives.postgresql.org/pgsql-performance/2008-01/msg1.php
we saw evidence that contention for SInvalLock was a problem,
and we (or at least I) concluded that the sinval messaging system
needed a nontrivial rewrite to get rid of its habit of sending everyon
