Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 373749FB2EF for ; Tue, 10 Oct 2006 14:09:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 45913-07 for ; Tue, 10 Oct 2006 14:09:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 80AF39FB2CC for ; Tue, 10 Oct 2006 14:09:54 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k9AH9q3K025954; Tue, 10 Oct 2006 13:09:52 -0400 (EDT) To: Tobias Brox cc: pgsql-performance@postgresql.org Subject: Re: long running transactions 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> Comments: In-reply-to Tobias Brox message dated "Tue, 10 Oct 2006 19:06:39 +0200" Date: Tue, 10 Oct 2006 13:09:52 -0400 Message-ID: <25953.1160500192@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.091 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200610/198 X-Sequence-Number: 21327 Tobias Brox 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