| From: | Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: reindexdb dying with SIGPIPE on 8.2.5 |
| Date: | 2008-12-21 20:21:05 |
| Message-ID: | 200812212121.05678@zmi.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Freitag 19 Dezember 2008 Alvaro Herrera wrote:
> You don't need to vacuum or reindex after a cluster; it removes all
> dead rows (except those that vacuum won't remove anyway)
OK, but I do not cluster all tables, as it only makes sense for tables
which get read in some sequential (based on that index) way. For
completely random accessed tables I skip cluster, and rely on
vacuum/reindex. Also, I think pg_toast tables cannot be clustered,
right?
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-12-22 00:46:48 | Re: reindexdb dying with SIGPIPE on 8.2.5 |
| Previous Message | John Lister | 2008-12-21 08:03:09 | Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron |