| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bill Chandler <billybobc1210(at)yahoo(dot)com> |
| Cc: | Mischa Sandberg <mischa(dot)sandberg(at)telus(dot)net>, pgsql-perform <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Index bloat problem? |
| Date: | 2005-04-21 23:56:18 |
| Message-ID: | 200504211656.18324.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Bill,
> If I deleted 75% of the rows but had a max_fsm_pages
> setting that still exceeded the pages required (as
> indicated in VACUUM output), would that solve my
> indexing problem or would I still need to REINDEX
> after such a purge?
Depends on the performance you're expecting. The FSM relates the the re-use
of nodes, not taking up free space. So after you've deleted 75% of rows,
the index wouldn't shrink. It just wouldn't grow when you start adding rows.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Enrico Weigelt | 2005-04-22 00:06:15 | foreign key performance |
| Previous Message | John A Meinel | 2005-04-21 23:54:08 | Re: Index bloat problem? |