Re: Bug in VACUUM reporting of "removed %d row versions" in 9.2+

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Bug in VACUUM reporting of "removed %d row versions" in 9.2+
Дата
Msg-id CA+U5nMLBUjUz9HR0yqmTLq523MreEtqSkDb3j1KAhxhGnMQU_g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Bug in VACUUM reporting of "removed %d row versions" in 9.2+  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
On 9 December 2013 21:24, Bruce Momjian <bruce@momjian.us> wrote:
>
> Where are we on this?

Good question, see below.

>> In those commits, lazy_vacuum_heap() skipped pinned blocks, but then
>> failed to report that accurately, claiming that the tuples were
>> actually removed when they were not. That bug has masked the effect of
>> the page skipping behaviour.

Wow, this is more complex than just that. Can't foresee backpatching anything.

We prune rows down to dead item pointers. Then we remove from the
index, then we try to remove them from heap, but may skip removal for
some blocks.

The user description of that is just wrong and needs more thought and work.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Compression of tables
Следующее
От: KONDO Mitsumasa
Дата:
Сообщение: Re: Optimize kernel readahead using buffer access strategy