Re: non-HOT update not looking at FSM for large tuple update

Поиск
Список
Период
Сортировка
От John Naylor
Тема Re: non-HOT update not looking at FSM for large tuple update
Дата
Msg-id CAFBsxsG8WWq9oNFbQon3rBPWTYrQSwYNmzjbp8a92BCg6vO5iQ@mail.gmail.com
обсуждение исходный текст
Ответы Re: non-HOT update not looking at FSM for large tuple update  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
Список pgsql-hackers
On Fri, Mar 12, 2021 at 8:45 AM Matthias van de Meent <boekewurm+postgres@gmail.com> wrote:
>
> If this case isn't added, the lower else branch will fail to find
> fitting pages for len > maxPaddedFsmRequest tuples; potentially
> extending the relation when there is actually still enough space
> available.

Okay, with that it looks better to go back to using Max().

Also in v4:

- With the separate constant you suggested, I split up the comment into two parts.
- I've added a regression test to insert.sql similar to your earlier test, but we cannot use vacuum, since in parallel tests there could still be tuples visible to other transactions. It's still possible to test almost-all-free by inserting a small tuple. 
- Draft commit message

--
John Naylor
EDB: http://www.enterprisedb.com
Вложения

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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: VACUUM (DISABLE_PAGE_SKIPPING on)
Следующее
От: John Naylor
Дата:
Сообщение: Re: WIP: BRIN multi-range indexes