From: | "jody brownell" <jody(dot)brownell(at)q1labs(dot)com> |
---|---|
To: | "Csaba Nagy" <nagy(at)ecircle-ag(dot)com> |
Cc: | "postgres performance list" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Help tuning autovacuum - seeing lots of relationbloat |
Date: | 2006-06-21 16:49:49 |
Message-ID: | 200606211349.49305.jody.brownell@q1labs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
block and row are always configured on - they are my friend :)
thanks
On Wednesday 21 June 2006 13:44, Csaba Nagy wrote:
> On Wed, 2006-06-21 at 18:39, jody brownell wrote:
> > that is exactly what I am seeing, one process, no change, always in idle while the others are constantly
> > changing their state.
> >
> > looks like someone opened a tx then is blocking on a queue lock or something. dang.
>
> Don't forget to check the statistics collector settings (see below), if
> that is not correct then autovacuum is indeed not working correctly... I
> should have put that on the beginning of the mail so you won't overlook
> it ;-)
>
> > >
> > > Oh, just occured to me... in order to use autovacuum you also need to
> > > enable the statistics collector on row level:
> > >
> > > stats_start_collector = on
> > > stats_row_level = on
> > >
> > > See also:
> > > http://www.postgresql.org/docs/8.1/static/maintenance.html#AUTOVACUUM
> > >
> > > This was not mentioned in the settings in your original post, so I guess
> > > you didn't touch that, and I think they are disabled by default.
> > >
> > > If this is disabled, you should enable it and "pg_ctl reload ....", that
> > > should fix the problem.
> > >
> > > Cheers,
> > > Csaba.
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-06-21 17:03:41 | Re: Speeding up query, Joining 55mil and 43mil records. |
Previous Message | Csaba Nagy | 2006-06-21 16:44:39 | Re: Help tuning autovacuum - seeing lots of relationbloat |