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

Re: reindexdb dying with SIGPIPE on 8.2.5

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: reindexdb dying with SIGPIPE on 8.2.5
Date: 2008-12-22 00:46:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Michael Monnerie wrote:
> 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.

Right -- I'm just saying that if you cluster a table, you don't need to
vacuum it.  Of course, you need to vacuum all the other tables.

>  Also, I think pg_toast tables cannot be clustered, right?

Not directly, but if you cluster a plain table, its toast table is
clustered too.

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.

In response to

pgsql-admin by date

Next:From: Laszlo NagyDate: 2008-12-22 10:11:30
Subject: Re: rebellious pg stats collector (reopened case)
Previous:From: Michael MonnerieDate: 2008-12-21 20:21:05
Subject: Re: reindexdb dying with SIGPIPE on 8.2.5

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