Re: Time limit for a process to hold Content lock in Buffer Cache - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Time limit for a process to hold Content lock in Buffer Cache
Date
Msg-id 16026.1369322170@sss.pgh.pa.us
Whole thread Raw
In response to Re: Time limit for a process to hold Content lock in Buffer Cache  (Atri Sharma <atri.jiit@gmail.com>)
Responses Re: Time limit for a process to hold Content lock in Buffer Cache  (Atri Sharma <atri.jiit@gmail.com>)
List pgsql-hackers
Atri Sharma <atri.jiit@gmail.com> writes:
>> 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.

No, you're not following.  These would be table-level heavyweight locks,
and there already are timeout mechanisms that work at that level.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Move unused buffers to freelist
Next
From: Amit Langote
Date:
Subject: Re: Time limit for a process to hold Content lock in Buffer Cache