X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 50A913A46C5 for ; Fri, 12 Nov 2004 15:30:48 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 35085-06 for ; Fri, 12 Nov 2004 15:30:34 +0000 (GMT) Received: from mail713.megamailservers.com (mail713.megamailservers.com [69.49.98.23]) by svr1.postgresql.org (Postfix) with ESMTP id 699B83A469E for ; Fri, 12 Nov 2004 15:30:32 +0000 (GMT) X-Authenticated-User: paul.pnlassociates.com Received: from [69.3.2.106] (h-69-3-2-106.mclnva23.covad.net [69.3.2.106]) (authenticated bits=0) by mail713.megamailservers.com (8.12.10/8.12.9) with ESMTP id iACFUSKK006910 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Fri, 12 Nov 2004 10:30:31 -0500 Message-ID: <4194D713.3000402@pnlassociates.com> Date: Fri, 12 Nov 2004 10:30:27 -0500 From: "Paul B. Anderson" User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Large transaction problem References: <4193C282.2040904@pnlassociates.com> <11555.1100207255@sss.pgh.pa.us> <4193E45A.7050000@pnlassociates.com> <20041112143349.GA32479@phlogiston.dyndns.org> In-Reply-To: <20041112143349.GA32479@phlogiston.dyndns.org> Content-Type: multipart/alternative; boundary="------------030207030404060001060208" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=HTML_20_30, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: * X-Archive-Number: 200411/104 X-Sequence-Number: 15489 This is a multi-part message in MIME format. --------------030207030404060001060208 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit When the vacuum full timed out, could the exclusive lock have been left set, leaving the database in an unusable state? BTW, thanks. I removed the --full option. Paul Andrew Sullivan wrote: >On Thu, Nov 11, 2004 at 05:14:50PM -0500, Paul B. Anderson wrote: > > >> /usr/bin/vacuumdb --all --full --analyze >> >> > ^^^^^ > >You do realise that takes an exclusive lock, right? Why are you >doing VACUUM FULL? If your FSM is set right, you really shouldn't >need it for most cases. > >A > > > --------------030207030404060001060208 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit When the vacuum full timed out, could the exclusive lock have been left set, leaving the database in an unusable state?

BTW, thanks.  I removed the --full option. 

Paul


Andrew Sullivan wrote:
On Thu, Nov 11, 2004 at 05:14:50PM -0500, Paul B. Anderson wrote:
  
 /usr/bin/vacuumdb --all --full --analyze
    
                            ^^^^^

You do realise that takes an exclusive lock, right?  Why are you
doing VACUUM FULL?  If your FSM is set right, you really shouldn't
need it for most cases.

A

  
--------------030207030404060001060208--