Isabelle Therrien <therriei@LUB.UMontreal.CA> writes:
> I have a big query, reported below, that is called several times in my
> application.
> At least 4 active connections call it at the same time.
> Normally, this query is executed in about 30-50 milliseconds.
> But after a while (depending on how many connections are used, and how
> often the query is called),
> the query is executed in 1000ms, then 2000ms, and it continues to grow
> exponentially. I've already seen it reaching 80 seconds.
Hmm, that's odd. What causes the time to drop back down to milliseconds
--- do you have to restart the whole database, or just run it in a new
backend? Does the amount of memory being used by the backend increase
as the time goes up? What does EXPLAIN show as the query plan for the
query? How large are the tables, and how many tuples are actually
retrieved?
Also, which beta release exactly, and how did you build it (what
configure options)?
Finally, it would be nice to see the full schemas for these tables, to
be sure we're not missing something. You can generate those via
pg_dump -s -t tablename databasename
regards, tom lane
