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

From The Hermit Hacker
Subject Re: Vacuum now uses AccessShareLock for analyze
Date
Msg-id Pine.BSF.4.21.0005291311470.608-100000@thelab.hub.org
Whole thread Raw
In response to Vacuum now uses AccessShareLock for analyze  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Vacuum now uses AccessShareLock for analyze
List pgsql-hackers
On Mon, 29 May 2000, Bruce Momjian wrote:

> I have changed vacuum so analyze now uses AccessShareLock.  (Is this the
> proper lock for analyze?)
> 
> 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.

hrmmm, here's a thought ... why not vacuum->analyze each relation in
order?  the 'exclusive lock' will prevent anyone from reading, so do a
relation, release the lock to analyze that relation and let ppl access the
database ... then do the next ... instead of doing an exclusive lock for
the duration of the whole database ...




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Additional system indexes
Next
From: Bruce Momjian
Date:
Subject: Re: Vacuum now uses AccessShareLock for analyze