Re: [PATCH] Refactoring of LWLock tranches
От | Robert Haas |
---|---|
Тема | Re: [PATCH] Refactoring of LWLock tranches |
Дата | |
Msg-id | CA+TgmobeXcVQK5ODx+yFjAEWm2oEE1KNr1Ek1JYUZ6wZZiJ51g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Refactoring of LWLock tranches (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: [PATCH] Refactoring of LWLock tranches
Re: [PATCH] Refactoring of LWLock tranches |
Список | pgsql-hackers |
On Thu, Feb 4, 2016 at 7:00 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: > [ new patch ] I've committed this after heavy rewriting. In particular, I merged two loops, used local variables to get rid of the very long and quite repetitive lines, and did various cleanup on the documentation and comments. I think we ought to move the buffer mapping, lock manager, and predicate lock manager locks into their own tranches also, perhaps using this new named-tranche facility. In addition, I think we should get rid of NumLWLocks(). It's no longer calculating anything; it just returns NUM_FIXED_LWLOCKS, and with the changes described in the first sentence of this paragraph, it will simply return NUM_INDIVIDUAL_LWLOCKS. We don't need a function just to do that; the assignment it does can be moved to the relevant caller. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: