Re: Vacuum improvement

From: Greg Copeland <greg(at)CopelandConsulting(dot)Net>
To: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
Cc: PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Vacuum improvement
Date: 2002-10-16 01:34:01
Message-ID: 1034732043.2517.614.camel@mouse.copelandconsulting.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-10-16 02:41:39 Re: droped out precise time calculations in src/interfaces/libpq/fe-connect.c
Previous Message Bruce Momjian 2002-10-16 01:18:34 Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.)