Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id E232D632306 for ; Tue, 13 Jan 2009 18:05:59 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 99103-05-5 for ; Tue, 13 Jan 2009 18:05:55 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by mail.postgresql.org (Postfix) with ESMTP id 1960263223D for ; Tue, 13 Jan 2009 18:05:51 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-85-214-61.bk4-dsl.surnet.cl [200.85.214.61]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id n0DMAIKe007631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jan 2009 14:11:16 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id A8C4E47CD5; Tue, 13 Jan 2009 19:04:13 -0300 (CLST) Date: Tue, 13 Jan 2009 19:04:13 -0300 From: Alvaro Herrera To: Tom Lane Cc: Scott Whitney , pgsql-admin@postgresql.org Subject: Re: Strange deadlock error last night Message-ID: <20090113220413.GI4005@alvh.no-ip.org> References: <20090113173555.80E667E4FD8@mail.int.journyx.com> <1307.1231880657@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1307.1231880657@sss.pgh.pa.us> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 13 Jan 2009 14:11:17 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/37 X-Sequence-Number: 31084 Tom Lane wrote: > "Scott Whitney" writes: > > It ended up locking up about 250 customer databases until I restarted the > > postmaster. This is version 8.1.4. Upgrading right now (even to a minor rev) > > is not really an option. > > Not related to the immediate problem, but: you really need to schedule > 5 minutes' downtime so you can update to 8.1.latest. Reasons can be > found here: > http://www.postgresql.org/docs/8.1/static/release.html Particularly so if you run autovacuum, because otherwise you'll be hit by a bug fixed in 8.1.6 about template0 being unfrozen (thawed?) -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support