From: Tobias Brox <tobias@nordicbet.com>
To: Csaba Nagy <nagy@ecircle-ag.com>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: slow queue-like empty table
Date: Wed, 4 Oct 2006 12:59:10 +0200
Message-ID: <20061004105910.GE12527@oppetid.no> (raw)
In-Reply-To: <1159433135.3874.204.camel@coppola.muc.ecircle.de>
References: <20060928065631.GA28138@oppetid.no>
<20060928073636.GG14672@oppetid.no>
<1159433135.3874.204.camel@coppola.muc.ecircle.de>
[Csaba Nagy - Thu at 10:45:35AM +0200]
> So you should check for "idle in transaction" sessions, those are bad...
> or any other long running transaction.
Thank you (and others) for pointing this out, you certainly set us on
the right track. We did have some few unclosed transactions;
transactions not beeing ended by "rollback" or "commit". We've been
fixing this, beating up the programmers responsible and continued
monitoring.
I don't think it's only due to those queue-like tables, we've really
seen a significant improvement on the graphs showing load and cpu usage
on the database server after we killed all the "idle in transaction". I
can safely relax still some weeks before I need to do more optimization
work :-)
(oh, btw, we didn't really beat up the programmers ... too big
geographical distances ;-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tobias@nordicbet.com, nagy@ecircle-ag.com
Subject: Re: slow queue-like empty table
In-Reply-To: <20061004105910.GE12527@oppetid.no>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox