Re: Unexpected VACUUM FULL failure

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: Unexpected VACUUM FULL failure
Дата
Msg-id 87d4xv2cz4.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Re: Unexpected VACUUM FULL failure  ("Simon Riggs" <simon@2ndquadrant.com>)
Ответы Re: Unexpected VACUUM FULL failure
Список pgsql-hackers
"Simon Riggs" <simon@2ndquadrant.com> writes:

> It would be better to release 8.3 with a new, clean, fast implementation
> of VF, than to release it with code that we *think* is right, but has so
> far proved a source of some truly obscure bugs.

Well building a suitable replacement for VACUUM FULL is more work than I was
proposing. The no-op ALTER TABLE rebuild still has the disadvantage of
requiring 2x the space taken by the table (and potentially more if you have
large indexes).

I also think it's a safer course of action to create a new command, spend one
or two releases improving it until we're sure it meets everyone's needs, then
drop the old command.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: regexp_split_to_array hangs backend
Следующее
От: Tom Lane
Дата:
Сообщение: regexp_matches and regexp_split are inconsistent