| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ben Young" <Ben(dot)Young(at)etrials(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Slow Restoration of a template1 Database (ALTER GROUP) |
| Date: | 2005-02-08 20:32:14 |
| Message-ID: | 9898.1107894734@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Ben Young" <Ben(dot)Young(at)etrials(dot)com> writes:
> Is the "index bloat" prevented/reduced in newer versions of Postgres?
Depends on what's causing it. Have you been inventing alphabetically
greater group names and getting rid of smaller names over time? If so,
this is a known problem that should be fixed in 7.4. The 7.4 release
notes say:
In previous releases, B-tree index pages that were left empty
because of deleted rows could only be reused by rows with index
values similar to the rows originally indexed on that page. In 7.4,
VACUUM records empty index pages and allows them to be reused for
any future index rows.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-02-09 09:14:49 | Re: query produces 1 GB temp file |
| Previous Message | Ben Young | 2005-02-08 20:08:50 | Re: Slow Restoration of a template1 Database (ALTER GROUP) |