Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager |
Дата | |
Msg-id | CA+TgmoZnWYQvmeqeGyY+0j-Tfmx8cTzRadfxJQwK9A-nCQ7GkA@mail.gmail.com обсуждение исходный текст |
Ответ на | [HACKERS] Moving relation extension locks out of heavyweight lock manager (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
|
Список | pgsql-hackers |
On Wed, May 10, 2017 at 8:39 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > Currently, the relation extension lock is implemented using > heavyweight lock manager and almost functions (except for > brin_page_cleanup) using LockRelationForExntesion use it with > ExclusiveLock mode. But actually it doesn't need multiple lock modes > or deadlock detection or any of the other functionality that the > heavyweight lock manager provides. I think It's enough to use > something like LWLock. So I'd like to propose to change relation > extension lock management so that it works using LWLock instead. That's not a good idea because it'll make the code that executes while holding that lock noninterruptible. Possibly something based on condition variables would work better. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: