Claudio Freire wrote:
> Stephen Frost wrote:
>> Rajesh Kumar. Mallah (mal...@tradeindia.com) wrote:
>>> we are actually also running out db max connections (also)
>>> ( which is currently at 600) , when that happens something at
>>> the beginning of the application stack also gets dysfunctional
It looks like this effect only occurs in the middle of the night when there
is some kind of automated dump process going on and the system is under
higher than normal load. I haven't managed to reproduce them outside of
production, but since these oddities don't seem to show up during normal
operat
> If I am correct, JDBC uses named portal only on the 5th time you use
> PreparedStatement (configurable). Before it uses unnamed thing that should
> work as if you did embed the value.
If this is due to the difference in parameter type information, this
doesn't have anything to do with named port
Murat Tasan writes:
> p.s. on the 8.4 version EXPLAIN ANALYZE *still* tells me that an
> external merge on disk is happening, despite my setting of work_mem to
> a full 16 MB this time.
When we have to push sort data to disk, it's written in a form that's
noticeably more compact than what's used
Chris Rimmer writes:
> While investigating some performance issues I have been looking at slow
> queries logged to the postgresql.log file. A strange thing that I have
> seen is a series of apparently very slow queries that just select from a
> sequence. It is as if access to a sequence is blocke
While investigating some performance issues I have been looking at slow
queries logged to the postgresql.log file. A strange thing that I have
seen is a series of apparently very slow queries that just select from a
sequence. It is as if access to a sequence is blocked for many sessions and
then r
If I am correct, JDBC uses named portal only on the 5th time you use
PreparedStatement (configurable). Before it uses unnamed thing that
should work as if you did embed the value. So the solution is to
recreate PreparedStatement each time (so you will have no problems with
SQL injection). Note
