Re: Vacuum improvement - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Vacuum improvement
Date
Msg-id 1034741804.11606.5.camel@rh72.home.ee
Whole thread Raw
In response to Vacuum improvement  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: Vacuum improvement  (Gavin Sherry <swm@linuxworld.com.au>)
Re: Vacuum improvement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 2002-10-16 at 05:22, Gavin Sherry wrote:
> Hi all,
> 
> I'm thinking that there is an improvement to vacuum which could be made
> for 7.4. VACUUM FULLing large, heavily updated tables is a pain. There's
> very little an application can do to minimise dead-tuples, particularly if
> the table is randomly updated. Wouldn't it be beneficial if VACUUM could
> have a parameter which specified how much of the table is vacuumed. That
> is, you could specify:
> 
> VACUUM FULL test 20 precent;

What about

VACUUM FULL test WORK 5 SLEEP 50;

meaning to VACUUM FULL the whole table, but to work in small chunks and
relaese all locks and let others access the tables between these ?

You could even fire up a separate thread to 

VACUUM [FULL] test WORK 5 SLEEP 50 CONTINUOUS;

To keep vacuuming a heavily updated table.

------------------
Hannu




pgsql-hackers by date:

Previous
From: Anuradha Ratnaweera
Date:
Subject: Re: Postgresql and multithreading
Next
From: "Shridhar Daithankar"
Date:
Subject: Re: Postgresql and multithreading