Re: Vacuum now uses AccessShareLock for analyze

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Vacuum now uses AccessShareLock for analyze
Date: 2000-05-29 17:08:17
Message-ID: 200005291708.NAA14150@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-05-29 17:11:38 Configuration and build clean-up
Previous Message Tom Lane 2000-05-29 17:05:35 Re: Vacuum now uses AccessShareLock for analyze