From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tobias Brox <tobias@nordicbet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: long running transactions
Date: Tue, 10 Oct 2006 13:09:52 -0400
Message-ID: <25953.1160500192@sss.pgh.pa.us> (raw)
In-Reply-To: <20061010170639.GB5360@oppetid.no>
References: <20061010161027.GA18908@oppetid.no>
<25404.1160497420@sss.pgh.pa.us>
<20061010163913.GA8097@oppetid.no>
<20061010164142.GA5360@oppetid.no>
<25631.1160498572@sss.pgh.pa.us>
<20061010170639.GB5360@oppetid.no>
Tobias Brox <tobias@nordicbet.com> writes:
>> Blocked on someone else's lock, maybe?
> hardly, the autovacuum is the only one having such a low transaction id,
> and also the only one hanging around when waiting a bit and rechecking
> the pg_locks table.
Hmph. Is the autovac process actually doing anything (strace would be
revealing)? If not, can you attach to the autovac process with gdb and
get a stack trace to see where it's blocked?
regards, tom lane
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: tgl@sss.pgh.pa.us, tobias@nordicbet.com
Subject: Re: long running transactions
In-Reply-To: <25953.1160500192@sss.pgh.pa.us>
* 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