Re: [HACKERS] Autovacuum loose ends

From: "Michael Paesold" <mpaesold(at)gmx(dot)at>
To: "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Autovacuum loose ends
Date: 2005-07-30 13:42:15
Message-ID: 02b901c5950c$7f85d2b0$8802460a@zaphod
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Alvaro Herrera wrote:

> I still haven't added custom cost-based delays, but I don't see that as
> a showstopper for removing it. I just went through the CVS log and I
> don't see anything else that applies.

I think you should at least add an autovacuum specific value for
"vacuum_cost_delay" because it turns cost-based vacuum delay on or off. I
believe not many will have vacuum_cost_delay enabled in postgresql.conf, but
will want to enable it for autovacuum.
At least I do.

Best Regards,
Michael Paesold

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2005-07-30 13:47:33 Win32 build broken by recent changes to xlog.c
Previous Message Andreas Pflug 2005-07-30 08:25:02 Re: Chocked

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2005-07-30 13:47:33 Win32 build broken by recent changes to xlog.c
Previous Message Omar Kilani 2005-07-30 07:28:18 Re: INSERT ... RETURNING