Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?
Дата
Msg-id CAH2-Wznyb4m1h40DycQqaDe3a3z=YkdsGGGfcX+YjC8J64d7=A@mail.gmail.com
обсуждение исходный текст
Ответ на Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?
Список pgsql-hackers
On Sat, Feb 8, 2025 at 8:47 AM Michail Nikolaev
<michail.nikolaev@gmail.com> wrote:
> Just some commit messages + few cleanups.

I'm worried about this:

+These longer pin lifetimes can cause buffer exhaustion with messages like "no
+unpinned buffers available" when the index has many pages that have similar
+ordering; but future work can figure out how to best work that out.

I think that we should have some kind of upper bound on the number of
pins that can be acquired at any one time, in order to completely
avoid these problems. Solving that problem will probably require GiST
expertise that I don't have right now.

--
Peter Geoghegan



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