I also have a client suffering an occasional 'application hang' running
Suse 11.2 and postgressql 8.4 on an 8 core box which is not reproducable
in a VMWare test environment.
Access to postgres is libpq 127.0.0.1 as well. Unfortunately the client
must restart ASAP and I have not produced a 'test
I'm just a lowly end user. Bumping the default statistics target or
using ALTER TABLE SET STATISTICS has made large differences in query
performance on large tables.
The query planner has to guesstimate using the statistics. Sometimes on
large tables the guesstimate isn't very good with a small
My experience using PQexecParams is
that it has a performance degradation of a factor of 100’s if not
thousands.
I have reworked my queries to DECLARE a binary cursor for
the return results and using a fixed text statement for the PQexec
select.
It doesn’t help on Inserts and Updates but
