Re: Resource Owner reassign Locks
Amit Kapila <amit.kapila@huawei.com>
From: Amit Kapila <amit.kapila@huawei.com>
To: "'Heikki Linnakangas'" <heikki.linnakangas@enterprisedb.com>, "'Jeff Janes'" <jeff.janes@gmail.com>
Cc: "'pgsql-hackers'" <pgsql-hackers@postgresql.org>
Date: 2012-06-19T06:02:50Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add a small cache of locks owned by a resource owner in ResourceOwner.
- eeb6f37d89fc 9.3.0 cited
> And it doesn't seem right for ResourceOwnerRemember/ForgetLock to have to accept a NULL owner. I am not sure, if it can ever enter into this flow without resowner as mentioned in jeff comments for session level locks. If it cannot enter then it is okay. > Please take a look to see if I broke something. In you previous mail you agreed with level as ERROR for elog message in function ResourceOwnerForgetLock(..) function, but in your modification you have used PANIC, is there any specific reason for it. With Regards, Amit Kapila.