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: | 20081222004648.GC8720@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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 http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Laszlo Nagy | 2008-12-22 10:11:30 | Re: rebellious pg stats collector (reopened case) |
Previous Message | Michael Monnerie | 2008-12-21 20:21:05 | Re: reindexdb dying with SIGPIPE on 8.2.5 |