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

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Kapila <amit(dot)kapila(at)huawei(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 15:08:37
Message-ID: CAOeZViejm=tFU=SQaL_DcBbpYMQU9s7BB=4zFRgpLM8x4HjSBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> For instance, take out exclusive locks on all your tables and just
> go to sleep (although I think this is limited by table permissions in
> recent PG versions).

This is what I have been worried about. The locks(exclusive locks or
content locks in buffers) can be held and stalled. Cant we do anything
about it? This is why I contemplated the timeout part.

Regards,

Atri

--
Regards,

Atri
l'apprenant

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-05-23 15:14:39 Re: Move unused buffers to freelist
Previous Message Tom Lane 2013-05-23 15:01:01 Re: Time limit for a process to hold Content lock in Buffer Cache