Re: reindexdb dying with SIGPIPE on 8.2.5

Поиск
Список
Период
Сортировка
Искать
От
Alvaro Herrera
Тема
Re: reindexdb dying with SIGPIPE on 8.2.5
Дата
Msg-id
20081222004648.GC8720@alvh.no-ip.org
Ответ на
Список
Дерево обсуждения
reindexdb dying with SIGPIPE on 8.2.5 Torsten Luettgert <t.luettgert@pressestimmen.de>
Re: reindexdb dying with SIGPIPE on 8.2.5 Michael Monnerie <michael.monnerie@is.it-management.at>
Re: reindexdb dying with SIGPIPE on 8.2.5 Guillaume Lelarge <guillaume@lelarge.info>
Re: reindexdb dying with SIGPIPE on 8.2.5 Michael Monnerie <michael.monnerie@is.it-management.at>
Re: reindexdb dying with SIGPIPE on 8.2.5 Alvaro Herrera <alvherre@commandprompt.com>
Re: reindexdb dying with SIGPIPE on 8.2.5 Michael Monnerie <michael.monnerie@is.it-management.at>
Re: reindexdb dying with SIGPIPE on 8.2.5 Alvaro Herrera <alvherre@commandprompt.com>
Re: reindexdb dying with SIGPIPE on 8.2.5 Tom Lane <tgl@sss.pgh.pa.us>
Re: reindexdb dying with SIGPIPE on 8.2.5 Torsten Luettgert <t.luettgert@pressestimmen.de>
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.
В списке pgsql-admin по дате отправления
От: Michael Monnerie
Дата:
От: Laszlo Nagy
Дата:
FAQ