Re: Vacuum now uses AccessShareLock for analyze - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Vacuum now uses AccessShareLock for analyze
Date
Msg-id 200005291708.NAA14150@candle.pha.pa.us
Whole thread Raw
In response to Re: Vacuum now uses AccessShareLock for analyze  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > The code will now vacuum all requested relations.  It will then analyze
> > each relation.  This way, all the exclusive vacuum work is done first,
> > then analyze can continue with shared locks.
> 
> I agree with Marc: it'd make more sense to do it one table at a time,
> ie,
>     get exclusive lock on table A
>     vacuum table A
>     commit, release lock
>     get shared lock on table A
>     gather stats for table A
>     commit, release lock
>     repeat sequence for table B
>     etc

OK, changed.

I will work on the additional issues in the next week or so.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Vacuum now uses AccessShareLock for analyze
Next
From: Tom Lane
Date:
Subject: Re: pg_* files are too large for empty database.