| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Autovacuum on by default? |
| Date: | 2006-08-23 07:26:27 |
| Message-ID: | 20060823072627.GK88878@pervasive.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 23, 2006 at 01:45:43PM +0900, ITAGAKI Takahiro wrote:
>
> "Jim C. Nasby" <jnasby(at)pervasive(dot)com> wrote:
>
> > And +1 on Rod's suggestion to make it more aggressive. I always drop the
> > scale factor to at least 0.2 and 0.1 (though 0.1 and 0.05 don't seem
> > unreasonable), and typically drop the thresholds to 200 and 100 (though
> > again, lower is probably warrented).
>
> The default fillfactors for index btree is 90%. So if we want to avoid
> spliting of the leaf pages, vacuum scale factors should be less than 0.1
> in cases where tuples are only updated randomly. I think threshoulds should
> be less than PCTFREEs(=1-fillfactors) except ever-increasing tables.
Very good point, though at least for indexes the new code that tries to
reclaim space on a page before splitting it will help. Doesn't help for
the heap, though.
So maybe the default should be 0.08?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2006-08-23 07:42:19 | Re: [HACKERS] COPY view |
| Previous Message | Jim C. Nasby | 2006-08-23 07:24:21 | Re: Autovacuum on by default? |