Re: lock_timeout GUC patch - Mailing list pgsql-hackers

From Boszormenyi Zoltan
Subject Re: lock_timeout GUC patch
Date
Msg-id 4B580811.4020607@cybertec.at
Whole thread Raw
In response to Re: lock_timeout GUC patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: lock_timeout GUC patch
List pgsql-hackers
Tom Lane írta:
> Robert Haas <robertmhaas@gmail.com> writes:
>   
>> 2010/1/20 Boszormenyi Zoltan <zb@cybertec.at>:
>>     
>>> Attached with the proposed modification to lift the portability concerns.
>>>       
>
>   
>> I think that it is a very bad idea to implement this feature in a way
>> that is not 100% portable.
>>     
>
> Agreed, this is not acceptable.  If there were no possible way to
> implement the feature portably, we *might* consider doing it like this.
> But I think more likely it'd get rejected anyway.  When there is a
> clear path to a portable solution, it's definitely not going to fly
> to submit a nonportable one.
>
>             regards, tom lane
>   

OK, I will implement it using setitimer().
It may not reach 8.5 though, when will this last Commitfest end?

Thanks,
Zoltán Böszörményi

-- 
Bible has answers for everything. Proof:
"But let your communication be, Yea, yea; Nay, nay: for whatsoever is more
than these cometh of evil." (Matthew 5:37) - basics of digital technology.
"May your kingdom come" - superficial description of plate tectonics

----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
http://www.postgresql.at/



pgsql-hackers by date:

Previous
From: Takahiro Itagaki
Date:
Subject: Re: Largeobject Access Controls (r2460)
Next
From: Leonardo F
Date:
Subject: Re: About "Our CLUSTER implementation is pessimal" patch