Skip site navigation (1) Skip section navigation (2)

Re: reindexdb dying with SIGPIPE on 8.2.5

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 (view raw or flat)
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


In response to

Responses

pgsql-admin by date

Next:From: Alvaro HerreraDate: 2008-12-22 00:46:48
Subject: Re: reindexdb dying with SIGPIPE on 8.2.5
Previous:From: John ListerDate: 2008-12-21 08:03:09
Subject: Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group