From: | "Medora Schauer" <mschauer(at)fairfield(dot)com> |
---|---|
To: | "Bill Moran" <wmoran(at)collaborativefusion(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: autovacuum not working? |
Date: | 2006-10-09 14:27:30 |
Message-ID: | 1CA058827877644DAB54FB930FFA3B05D89F73@lincoln.FAIRIND.FAIRFIELD.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> From: Bill Moran [mailto:wmoran(at)collaborativefusion(dot)com]
> In response to "Medora Schauer" <mschauer(at)fairfield(dot)com>:
>
> > I've recently moved to 8.1 and find that autovacuum doesn't seem to
be
> > working, at least not the way I expected it to. I need the tuple
count
> > for a table to be updated so indexes will be used when appropriate.
I
> > was expecting the tuples count for a table to be updated after
> > autovacuum ran. This doesn't seem to be the case. I added 511
records
> > to a previously empty table and waited over an hour. Tuples for the
> > table (as per pgaccess) was 0. After I did a manual vacuum analyze
it
> > went to 511.
>
> From your attached config file:
>
> #autovacuum_vacuum_threshold = 1000 # min # of tuple updates before
> # vacuum
>
Yup, that was it.
Thanks.
Medora
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2006-10-09 17:12:43 | Re: Simple join optimized badly? |
Previous Message | Merlin Moncure | 2006-10-09 14:19:13 | Re: Performance Optimization for Dummies 2 - the SQL |