Re: lock_timeout GUC patch - Review - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: lock_timeout GUC patch - Review
Date
Msg-id 4C56D18F0200002500034089@gw.wicourts.gov
Whole thread Raw
In response to Re: lock_timeout GUC patch - Review  (Marc Cousin <cousinmarc@gmail.com>)
Responses Re: lock_timeout GUC patch - Review
Re: lock_timeout GUC patch - Review
List pgsql-hackers
Marc Cousin <cousinmarc@gmail.com> wrote:
> This time, it's this case that doesn't work :
> I really feel that the timeout framework is the way to go here.
Since Zoltán also seems to feel this way:
http://archives.postgresql.org/message-id/4C516C3A.6090102@cybertec.at
I wonder whether this patch shouldn't be rejected with a request
that the timeout framework be submitted to the next CF.  Does anyone
feel this approach (without the framework) should be pursued
further?
-Kevin


pgsql-hackers by date:

Previous
From: Yeb Havinga
Date:
Subject: Re: patch for check constraints using multiple inheritance
Next
From: Boszormenyi Zoltan
Date:
Subject: Re: lock_timeout GUC patch - Review