Re: PATCH to allow concurrent VACUUMs to not lock each

From: Hannu Krosing <hannu(at)skype(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: PATCH to allow concurrent VACUUMs to not lock each
Date: 2005-05-23 09:49:42
Message-ID: 1116841783.4849.5.camel@fuji.krosing.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On K, 2005-05-18 at 11:54 +0300, Hannu Krosing wrote:
> The attached patch allows VACUUMS's on small relations to clean up dead
> tuples while VACUUM or ANALYSE is running for a long time on some big
> table.
>
> This is done by adding a "bool inVacuum" to PGPROC and then making use
> of it in GetOldestXmin.
>
> This patch is against current CVS head, but should also apply to 8.0.2
> with minorpach warnings.

Could this patch be applied (or rejected if something is badly wrong
with it) ?

Or should I move the discussion back to pgsql-hackers ad try to make it
a TODO first ?

This patch implements what I described in
http://archives.postgresql.org/pgsql-hackers/2005-05/msg00704.php
plus a small change to make it work for simple ANALYSE too.

--
Hannu Krosing <hannu(at)skype(dot)net>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message José Orlando Pereira 2005-05-23 10:00:19 Re: Two-phase commit issues
Previous Message Zeljko Vrba 2005-05-23 06:12:35 subquery returning array

Browse pgsql-patches by date

  From Date Subject
Next Message Qingqing Zhou 2005-05-23 10:52:43 psql: \d+ show tablespace of indices
Previous Message Mahmoud Taghizadeh 2005-05-23 07:47:21 modified farsi faq in html and txt version