Skip site navigation (1) Skip section navigation (2)

Re: Large transaction problem

From: "Paul B(dot) Anderson" <paul(at)pnlassociates(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Large transaction problem
Date: 2004-11-12 15:30:27
Message-ID: 4194D713.3000402@pnlassociates.com (view raw or flat)
Thread:
Lists: pgsql-admin
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
>
>  
>

In response to

Responses

pgsql-admin by date

Next:From: Andrew SullivanDate: 2004-11-12 15:57:28
Subject: Re: Large transaction problem
Previous:From: Andrew SullivanDate: 2004-11-12 14:33:49
Subject: Re: Large transaction problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group