| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev) |
| Cc: | scrappy(at)hub(dot)org, herouth(at)oumail(dot)openu(dot)ac(dot)il, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Re: [QUESTIONS] MySQL benchmark page\ |
| Date: | 1998-02-04 02:37:51 |
| Message-ID: | 199802040237.VAA01873@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> The Hermit Hacker wrote:
> >
> > So, why is pg_class locked for the duration of a vacuum when the
> > vacuum is being performed for the whole database when it should (I think)
> > only need to be locked when updates are happening to it?
>
> Yes, this is how it should be. This long lock comes from very old time.
> When I visited vacuum last time (year ago) I hadn't time to decide
> why this lock is here and could it be just removed or not.
> Still no time :)
>
> Vadim
>
>
Added to TODO:
* Make VACUUM on database not lock pg_class
* Make VACUUM ANALYZE only use a readlock
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vadim B. Mikheev | 1998-02-04 02:59:35 | Re: [HACKERS] Re: [QUESTIONS] MySQL benchmark page\ |
| Previous Message | Bruce Momjian | 1998-02-04 02:36:11 | Re: [QUESTIONS] timestamp questions |