| From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autovacuum next steps |
| Date: | 2007-02-19 11:31:15 |
| Message-ID: | 1171884675.3101.258.camel@coppola.muc.ecircle.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2007-02-19 11:58:47 | Re: Multiple Storage per Tablespace, or Volumes |
| Previous Message | Magnus Hagander | 2007-02-19 11:17:47 | Re: pg_proc without oid? |