Re: Avoid overhead open-close indexes (catalog updates)

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Avoid overhead open-close indexes (catalog updates)
Дата
Msg-id Y3SP/ZeubfnazUJO@paquier.xyz
обсуждение исходный текст
Ответ на Re: Avoid overhead open-close indexes (catalog updates)  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Avoid overhead open-close indexes (catalog updates)  (Ranier Vilela <ranier.vf@gmail.com>)
Список pgsql-hackers
On Wed, Nov 16, 2022 at 06:58:01AM +0900, Michael Paquier wrote:
> This one has been left out on purpose.  I was tempting to use
> WithInfo() with a CatalogIndexState opened optionally but I got the
> impression that it makes the code a bit harder to follow and
> AddRoleMems() is already complex on its own.  Most DDL patterns
> working on role would involve one role.  More roles could be added of
> course in one shot, but the extra logic complexity did not look that
> appealing to me especially as some role updates are skipped.

I have worked more on that today, and applied all that after splitting
the whole in three commits in total as different areas were touched.
It looks like we are good for this thread, then.

I have spotted more optimizations possible, particularly for operator
classes, but that could happen later.
--
Michael

Вложения

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

Предыдущее
От: Himanshu Upadhyaya
Дата:
Сообщение: Re: HOT chain validation in verify_heapam()
Следующее
От: John Naylor
Дата:
Сообщение: Re: [PoC] Improve dead tuple storage for lazy vacuum