Queries (both select and insert/update) against heavily indexed tables do most of the reads and writes to the index trees and relatively little reading and writing to the actual table data.
The index is completely redundant (read: rebuildable during restart) and its rebuild "should" be very parallelizable. Without the WAL and disk synchronization munching, even a single-threaded rebuild during restart should be fairly quick.
This would allow the index to stay in RAM. giving it a higher priority than all other disk objects in the OS cache. Putting it in pageable RAM would allow the OS to reclaim core if it absolutely had to.
Am I way off here?
---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
