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 15602.1369319513@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:
> On a different note, shouldn't we have a time out for a content lock
> in buffer cache?

No; the overhead of setting up and canceling such a timeout would
greatly outweigh any possible benefit.

Generally speaking, LWLocks are not meant to be used in situations where
the lock hold time might be long enough to justify worrying about
timeouts.  If you need that kind of behavior, use a heavyweight lock.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Chris Farmiloe
Date:
Subject: ASYNC Privileges proposal
Next
From: Atri Sharma
Date:
Subject: Re: Time limit for a process to hold Content lock in Buffer Cache