-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It is probably not really a pg issue that you don't get your CPUs fully
used. I would guess that one CPU saturates the memory bus or the disk
bandwidth depending on where your data is. This is the typical behavior
for memory bounded applications where
Folks,
Im hoping someone can give me some pointers to resolving an issue with postgres and its ability to utilize multiple CPUs effectively.
The issue is that no matter how much query load we throw at our server it seems almost impossible to get it to utilize more than 50% cpu on a dual-cpu
