Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id CFA03632306 for ; Tue, 13 Jan 2009 18:16:35 -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 10953-06-3 for ; Tue, 13 Jan 2009 18:16:31 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mail.postgresql.org (Postfix) with ESMTP id 56E63632232 for ; Tue, 13 Jan 2009 18:16:20 -0400 (AST) Received: by rv-out-0506.google.com with SMTP id b25so216882rvf.43 for ; Tue, 13 Jan 2009 14:16:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=SyhoQRg5ZFX1hW1fz48JkIlXdVplQ6CE74NsR5KvnRc=; b=sGcsq0TG15shwnH1n2k5+ad9Fkc2iUgkXCDJPE2hYvwURtytzBqP1LSvvbznLRiDMO 4dmK88RrHTC9qJSuXoj9UKeRYV0UfSYKnw+zuCGnu9JSLKIkliuY/bI4zABuSMsxAz5e sy4urpEKWfNQuWLXe51KXy2uTcMJjODmt5DPs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=WkS5wYoJyWkJpHxJAD0VOBSVmt62yecGsa65IlENJU9G1tfDpg5LCr5O5JtJ4Iv9HF 4KL1PWFG0aGF4p4w0dZZkV+PilTYkP637+MGQgPcmUF38VH2Bxpcyoah3ZsCL5sI4iVj BmSzUnV8jFH2H1kudNw08el++mO06VS1LWh/I= Received: by 10.114.144.1 with SMTP id r1mr20647398wad.2.1231884979022; Tue, 13 Jan 2009 14:16:19 -0800 (PST) Received: by 10.114.38.7 with HTTP; Tue, 13 Jan 2009 14:16:18 -0800 (PST) Message-ID: Date: Tue, 13 Jan 2009 15:16:18 -0700 From: "Scott Marlowe" To: "Scott Whitney" Subject: Re: Strange deadlock error last night Cc: pgsql-admin@postgresql.org In-Reply-To: <20090113173555.80E667E4FD8@mail.int.journyx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20090113173555.80E667E4FD8@mail.int.journyx.com> 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/38 X-Sequence-Number: 31085 On Tue, Jan 13, 2009 at 10:37 AM, Scott Whitney wrote: > 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. This box has been up and running for 306 days. This > postgres level has been installed for..err...well...at least Aug 9, 2006, > based on some dates in the directories. You need to ask yourself how much downtime you can afford. The 2 or 3 minutes every few months to go from 8.1.x to 8.1.x+1, or the half a day of downtime when some horrendous bug takes down the whole site because you didn't update it. Seriously, that unfozen template0 bug that Alvarro mentioned is one of those kinds of bugs. Nothing like your db going down in the middle of the day with an error message that it's going down to prevent txid wraparound induced loss, please run vacuum on all your databases in single user mode. If you can't find set aside a minute or two at 0200 hrs, then don't be surprised when you get one of those failures.