On Thu, Sep 24, 2009 at 2:27 AM, <jesper@xxxxxxxx> wrote: > Hi. > > I have a transaction running at the database for around 20 hours .. still > isn't done. But during the last hours it has come to the point where it > really hurts performance of "other queries". What is your transaction doing during this time? > Given pg_stat_activity output there seems to be no locks interfering but > the overall cpu-usage of all queries continue to rise. iowait numbers are > also very low. What does select count(*) from pg_stat_activity where waiting; say? > What can I do to make the system handle other queries better? Really kinda depends on what your transaction is doing. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
