HI,
I have an application that maintains 150 open connections to a Postgres DB
server. The application works fine without a problem for the most time.
The problem seem to arise when a SELECT that returns a lot of rows is executed
or the SELECT is run on a large object. These selects are run
The problem seem to arise when a SELECT that returns a lot of rows is
Does the SELECT return a lot of rows, or does it scan a lot of rows ?
(for instance, if you use aggregates, it might scan lots of data but only
return few rows).
The problem is that when the SELECTs are run the main