Re: TOAST - why separate visibility map

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: TOAST - why separate visibility map
Дата
Msg-id 3172107.1637424982@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: TOAST - why separate visibility map  (Andres Freund <andres@anarazel.de>)
Ответы Re: TOAST - why separate visibility map  (Virender Singla <virender.cse@gmail.com>)
Список pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On November 19, 2021 12:31:00 PM PST, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It might be feasible to drop the visibility map for toast tables, though.

> I think it be a bad idea - the VM is used by vacuum to avoid rereading already vacuumed ranges. Loosing that for
largetoast tables would be bad. 

Ah, right.  I was thinking vacuuming depended on the other map fork,
but of course it needs this one.

In short, there are indeed good reasons why it works like this.

            regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Test::More version
Следующее
От: Hans Buschmann
Дата:
Сообщение: AW: VS2022: Support Visual Studio 2022 on Windows