Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 593169FB2F4 for ; Tue, 10 Oct 2006 14:13:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 92005-02 for ; Tue, 10 Oct 2006 17:13:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lynet.oppetid.no (oppetid.no [80.65.51.2]) by postgresql.org (Postfix) with ESMTP id 902CE9FB2EF for ; Tue, 10 Oct 2006 14:13:05 -0300 (ADT) Received: by lynet.oppetid.no (Postfix, from userid 1019) id 3FD25119FA8; Tue, 10 Oct 2006 19:13:04 +0200 (CEST) Date: Tue, 10 Oct 2006 19:13:04 +0200 From: Tobias Brox To: Tom Lane Cc: Tobias Brox , pgsql-performance@postgresql.org Subject: Re: long running transactions Message-ID: <20061010171304.GC5360@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> <25953.1160500192@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25953.1160500192@sss.pgh.pa.us> Organization: Group Nordicbet User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/199 X-Sequence-Number: 21328 [Tom Lane - Tue at 01:09:52PM -0400] > 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? Sorry ... I SIGINT'ed it, and now it's gone :-( I thought reloading the config would restart autovacuum. Well, whatever, we still have the nightly vacuum crontab.