Remember the suggestion I made that PostgreSQL add the capability
to define named caches and bind specific objects to those caches?
One of the reasons Sybase recommends using such named caches
(per their performance tuning documentation) is to reduce spinlock
contention.
I don't know whether PostgreSQL would get a similar benefit, but
this discussion rang a bell, so I thought I should throw it out there
on the chance that it might be useful.
-Kevin
>>> Tom Lane <tgl@sss.pgh.pa.us> >>>
The problem right now is not lack of ability to reproduce the
problem, it is lack of ideas how to fix it.