From: Tobias Brox <tobias@nordicbet.com>
To: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Long running transactions again ...
Date: Wed, 11 Apr 2007 00:50:37 +0200
Message-ID: <20070410225037.GC19909@oppetid.no> (raw)
We had problems again, caused by long running transactions. I'm
monitoring the pg_stat_activity view, checking the query_start of all
requests that are not idle - but this one slipped under the radar as the
application was running frequent queries towards the database.
That's not what concerns me most. We had two databases running under
postgres at this host - like, main production database (A) and a
separate smaller database for a separate project (B). As far as I
understood postgres philosophy, the databases should be isolated from
each other, i.e. one are not allowed to create a query that goes across
the database borders (select * from A.customers join B.logins ...). So,
I was surprised to see that the application working towards database B
managed to jam up database A, to the extent that we couldn't get A
vacuumed properly.
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
Subject: Re: Long running transactions again ...
In-Reply-To: <20070410225037.GC19909@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