Re: HOT patch - version 11
| От | Pavan Deolasee |
|---|---|
| Тема | Re: HOT patch - version 11 |
| Дата | |
| Msg-id | 2e78013d0708020033r64bb7522ge3221a2c33fd4eab@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: HOT patch - version 11 ("Pavan Deolasee" <pavan.deolasee@gmail.com>) |
| Список | pgsql-patches |
On 8/2/07, Pavan Deolasee <pavan.deolasee@gmail.com> wrote:
On 8/2/07, Heikki Linnakangas < heikki@enterprisedb.com> wrote:Maybe a nicer
solution would be to have another version of ConditionalLockBuffer with
three different return values: didn't get lock, got exclusive lock, or
got cleanup lock.
Thats a good idea. I shall do that.
On a second thought, I feel its may not be such a good idea to change
the ConditionalLockBuffer return value. "boolean" is the most natural
way. And we don't save anything in terms on BufHdr locking.
So may be should just have two different functions and do the
BufferIsLockedForCleanup check immediately after acquiring the
exclusive lock.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
В списке pgsql-patches по дате отправления: