| From: | "Larry Rosenman" <ler(at)lerctr(dot)org> |
|---|---|
| To: | "Jim Nasby" <jnasby(at)pervasive(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "'Jim C(dot) Nasby'" <jim(at)nasby(dot)net>, "'Alvaro Herrera'" <alvherre(at)alvh(dot)no-ip(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Autovacuum on by default? |
| Date: | 2006-08-24 13:35:03 |
| Message-ID: | 002301c6c782$1b92cfc0$0202fea9@aus.pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim C. Nasby wrote:
> On Tue, Aug 22, 2006 at 11:08:49AM -0400, Tom Lane wrote:
>> "Jim C. Nasby" <jim(at)nasby(dot)net> writes:
>>> If there's a bunch of activity on a table but stats are reset
>>> before a vacuum is run on it and then a vacuum is run, the user
>>> will still be left thinking that the table needs to be vacuumed.
>>
>> Except that autovac *won't* vacuum it if the stats have been reset.
>> So I'm not seeing that there's really a problem in practice.
>
> IIRC the stats also include info about regular (manual) vacuums, so
> the above scenario still applies.
They do. The stats patch as applied captures both autovacuum and manual
vacuum
as well as analyze (both from the Autovacuum daemon and manual).
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler(at)lerctr(dot)org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-08-24 13:38:43 | Re: Autovacuum on by default? |
| Previous Message | Gregory Stark | 2006-08-24 13:28:52 | Re: Tricky bugs in concurrent index build |