Re: performance issue in remove_from_unowned_list()
От | Robert Haas |
---|---|
Тема | Re: performance issue in remove_from_unowned_list() |
Дата | |
Msg-id | CA+TgmobHscKHVBLfZ0k43hXoq6vP8R5CB6i686jCZQtW7ASoaw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: performance issue in remove_from_unowned_list() (Tomas Vondra <tomas.vondra@2ndquadrant.com>) |
Ответы |
Re: performance issue in remove_from_unowned_list()
|
Список | pgsql-hackers |
On Tue, Mar 12, 2019 at 6:54 PM Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote: > Attached is a patch adopting the dlist approach - it seems to be working > quite fine, and is a bit cleaner than just slapping another pointer into > the SMgrRelationData struct. So I'd say this is the way to go. What about using a data structure that supports O(1) lookups for any element? The current efforts all seem to revolve around correctly guessing from which end of the list we are likely to delete stuff, but your research suggests that we don't always make such guesses particularly well. And it seems unnecessary. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: