From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Autovacuum on by default? |
Date: | 2006-08-17 17:47:37 |
Message-ID: | 44E4ABB9.3000306@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Matthew T. O'Connor wrote:
>
>> I assume you are suggesting that the base value be 0? Well for one
>> thing if the table doesn't have any rows that will result in constant
>> vacuuming of that table, so it needs to be greater than 0. For a small
>> table, say 100 rows, there usually isn'tn much performance impact if the
>> table if 50% dead space, so I think the base values you suggest are OK,
>> but they shouldn't be 0.
>>
>
> Actually Tom suggested some time ago that we should get rid of the base
> value completely, i.e. make it 0 forever.
>
> A row with 0 tables would not show any activity in pgstats, so it would
> not be vacuumed constantly. Only once after it's truncated.
OK, forgot that. Well I put it in originally as a way to give more
flexability to the calculation, if I want a tabled vacuumed every 100
updates, then I can set the scaling factor to 0 and the base value to
100, but maybe that's not really needed. It would simplify things if we
got rid of it.
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Mair | 2006-08-17 18:05:34 | Re: [HACKERS] selecting large result sets in psql using |
Previous Message | Alvaro Herrera | 2006-08-17 17:43:34 | Re: Autovacuum on by default? |