"Barry Lind" <blind@xythos.com> writes:
> ... On a hunch I switched the jdbc driver to using the V2 protocol
> and the load on the machine dropped down to what it was when using
> Oracle and everything was fine.
First knee-jerk reaction is that it's an optimization problem stemming
from V3 protocol feeding parameterized queries to the backend where V2
did not, and the planner being unable to cope :-(
Can you identify the specific queries causing the problem?
regards, tom lane