Re: [PATCH] Refactoring of LWLock tranches
От | Robert Haas |
---|---|
Тема | Re: [PATCH] Refactoring of LWLock tranches |
Дата | |
Msg-id | CA+TgmoZyU2bDO6i3S0UUkv74GCwchD1xEA-4gJJ6xPn5CWmLuQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Refactoring of LWLock tranches (Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru>) |
Ответы |
Re: [PATCH] Refactoring of LWLock tranches
|
Список | pgsql-hackers |
On Sun, Sep 13, 2015 at 5:05 PM, Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru> wrote: > Yes, that is because I tried to go with current convention working with > shmem in Postgres (there are one function that returns the size and > others that initialize that memory). But I like your suggestion about > API functions, in that case number of tranches and locks will be known > during the initialization. I also want to leave the door open to tranches that are registered after initialization. At that point, it's too late to put a tranche in shared memory, but you can still use DSM. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: