Re: autovacuum next steps - Mailing list pgsql-hackers

From Csaba Nagy
Subject Re: autovacuum next steps
Date
Msg-id 1171884675.3101.258.camel@coppola.muc.ecircle.de
Whole thread Raw
In response to Re: autovacuum next steps  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
> One option that I've heard before is to have vacuum after a single iteration
> (ie, after it fills maintenance_work_mem and does the index cleanup and the
> second heap pass), remember where it was and pick up from that point next
> time.

>From my experience this is not acceptable... I have tables for which the
index cleanup takes hours, so no matter how low I would set the
maintenance_work_mem (in fact I set it high enough so there's only one
iteration), it will take too much time so the queue tables get overly
bloated (not happening either, they get now special "cluster"
treatment).

Cheers,
Csaba.




pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pg_proc without oid?
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Multiple Storage per Tablespace, or Volumes