Re: Reviewing freeze map code

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Reviewing freeze map code
Дата
Msg-id 20160701204329.7bvfy2fu47fn4fjp@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: Reviewing freeze map code  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: Reviewing freeze map code  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
On 2016-07-01 15:42:22 -0500, Jim Nasby wrote:
> On 7/1/16 2:23 PM, Andres Freund wrote:
> > > > The only
> > > > cost of that is that vacuum will come along and mark the page
> > > > all-visible again instead of skipping it, but that's probably not an
> > > > enormous expense in most cases.
> > I think the main cost is not having the page marked as all-visible for
> > index-only purposes. If it's an insert mostly table, it can be a long
> > while till vacuum comes around.
> 
> ISTM that's something that should be addressed anyway (and separately), no?

Huh? That's the current behaviour in heap_lock_tuple.



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

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: Reviewing freeze map code
Следующее
От: Jim Nasby
Дата:
Сообщение: Re: Reviewing freeze map code