| From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
|---|---|
| To: | Erik Jones <erik(at)myemma(dot)com> |
| Cc: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: For index bloat: VACUUM ANALYZE vs REINDEX/CLUSTER |
| Date: | 2007-09-19 15:30:15 |
| Message-ID: | 162380.54690.qm@web31806.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Not quite. Once a page has reached it's fill factor percentage full,
> no more inserts will happen on that page, only updates. Also, I
> think you have large/small backwards wrt fill factor. If you have a
> fill factor of, say, 40% then once a page has reached 40% full no
> more inserts will happen (unless some space is reclaimed by vacuum).
> So, smaller fill factors == bigger holes. The bigger the fill
> factor, the smaller the whole: if you have a fill factor of 90%,
> only 10% is reserved for updates of rows on that page.
So (just to reiterate), fill factor can be applied to both a table and/or an index(es). But the
"holes" built into the page of a table or index can only be filled by UPDATE Statements.
Thanks for the clarification!
Regards,
Richard Broesma Jr.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bastien Continsouzas | 2007-09-19 15:32:50 | Re: Plpgsql function to join array elements with a string |
| Previous Message | Erik Jones | 2007-09-19 15:17:00 | Re: For index bloat: VACUUM ANALYZE vs REINDEX/CLUSTER |