Re: Time limit for a process to hold Content lock in Buffer Cache

From: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
To: "'Atri Sharma'" <atri(dot)jiit(at)gmail(dot)com>, "'Pg Hackers'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Time limit for a process to hold Content lock in Buffer Cache
Date: 2013-05-23 10:57:33
Message-ID: 004b01ce57a4$54bcde80$fe369b80$@kapila@huawei.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, May 23, 2013 3:35 PM Atri Sharma wrote:
> Hi all,
>
> I was searching for an existing mechanism which ensures that a crashed
> process releases a content lock held on a page in buffer cache. Also,
> a similar mechanism for refcount of the page.
>
> I seem to have missed it. Do we have a mechanism,and if yes,where can I
> find it?

On any process (backend, bgwriter,checkpointer, ..) crash, it reinitialize
the shared memory which will clear any locks held.
Please refer functions HandleChildCrash() and PostmasterStateMachine().

With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-05-23 11:10:08 pg_rewind, a tool for resynchronizing an old master after failover
Previous Message Mathieu Guerin 2013-05-23 10:06:15 WARNING : pgstat wait timeout - stats_temp_directory - postgres 9.1