Horton

Re: Resource Owner reassign Locks

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>

View thread
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Amit Kapila <amit.kapila@huawei.com>
Cc: 'Jeff Janes' <jeff.janes@gmail.com>, 'pgsql-hackers' <pgsql-hackers@postgresql.org>
Date: 2012-06-19T06:09:41Z
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 →

  1. Add a small cache of locks owned by a resource owner in ResourceOwner.

On 19.06.2012 09:02, Amit Kapila wrote:
>> 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.

Ah, sorry, that was just a debugging aid. Before posting the patch, I 
had a bug (now fixed) where I got that error, and I changed it 
temporarily to PANIC to get a core dump, but forgot to change it back 
before posting the patch. It should indeed be ERROR, not PANIC.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com