Re: Setting visibility map in VACUUM's second phase

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: Setting visibility map in VACUUM's second phase
Дата
Msg-id CAMkU=1y4joaSQAtJC_ekFa5VzBq7bYxGcYDEAxLRLu+BroYwnQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Setting visibility map in VACUUM's second phase  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Ответы Re: Setting visibility map in VACUUM's second phase  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Список pgsql-hackers
On Friday, December 7, 2012, Pavan Deolasee wrote:
 
Revised patch attached. This time much less invasive. I added a new
function heap_page_is_all_visible() to check if the given page is
all-visible and also return the visibility cutoff xid.

Hi Pavan,

lazy_vacuum_page now pins and unpins the vmbuffer for each page it marks all-visible, which seems like a lot of needless traffic since the next vmbuffer is likely to be the same as the previous one.

Could it instead get vmbuffer passed down to it from the two calling sites?   (One call site would have to have it introduced, just for this purpose, the other should be able to use its existing one.)

Cheers,

Jeff

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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: logical changeset generation v4 - Heikki's thoughts about the patch state
Следующее
От: Kohei KaiGai
Дата:
Сообщение: Re: [sepgsql 1/3] add name qualified creation label