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

From Boszormenyi Zoltan
Subject Re: lock_timeout GUC patch - Review
Date
Msg-id 4C57220A.7010108@cybertec.at
Whole thread Raw
In response to Re: lock_timeout GUC patch - Review  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: lock_timeout GUC patch - Review  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
Hi,

Kevin Grittner írta:
> 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?
>   

I certainly think so, the current scheme seems to be very fragile
and doesn't want to be extended.



pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: lock_timeout GUC patch - Review
Next
From: "Kevin Grittner"
Date:
Subject: Re: lock_timeout GUC patch - Review