Re: [PATCH] Refactoring of LWLock tranches
От | Alvaro Herrera |
---|---|
Тема | Re: [PATCH] Refactoring of LWLock tranches |
Дата | |
Msg-id | 20150923152254.GR295765@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: [PATCH] Refactoring of LWLock tranches (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [PATCH] Refactoring of LWLock tranches
|
Список | pgsql-hackers |
Robert Haas wrote: > On Tue, Sep 22, 2015 at 5:16 AM, Ildus Kurbangaliev > <i.kurbangaliev@postgrespro.ru> wrote: > > Yes, probably. > > I'm going to change API calls as you suggested earlier. > > How you do think the tranches registration after initialization should > > look like? > > I don't see any need to change anything there. The idea there is that > an extension allocates a tranche ID and are responsible for making > sure that every backend that uses that tranche finds out about the ID > that was chosen and registers a matching tranche definition. How to > do that is the extension's problem. Maybe eventually we'll provide > some tools to make that easier, but that's separate from the work > we're trying to do here. FWIW I had assumed, when you created the tranche stuff, that SLRU users would all allocate their lwlocks from a tranche provided by slru.c itself, and the locks would be stored in the slru Ctl struct. Does that not work for some reason? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: