Re: Vacuum improvement - Mailing list pgsql-hackers

From Greg Copeland
Subject Re: Vacuum improvement
Date
Msg-id 1034732043.2517.614.camel@mouse.copelandconsulting.net
Whole thread Raw
In response to Vacuum improvement  (Gavin Sherry <swm@linuxworld.com.au>)
List pgsql-hackers
That a good idea.  That way, if your database slows during specific
windows in time, you can vacuum larger sizes, etc.  Seemingly would help
you better manage your vacuuming against system loading.


Greg

On Tue, 2002-10-15 at 19: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;
>
> Yes, terrible syntax but regardless: this would mean that we could
> spread the vacuum out and not, possibly, be backing up queues. ANALYZE
> could be modified, if necessary.
>
> Thoughts?
>
> Gavin
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.)
Next
From: Tom Lane
Date:
Subject: Re: droped out precise time calculations in src/interfaces/libpq/fe-connect.c