Re: lock_timeout GUC patch

From: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Subject: Re: lock_timeout GUC patch
Date: 2010-01-21 07:53:53
Message-ID: 4B580811.4020607@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane írta:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>
>> 2010/1/20 Boszormenyi Zoltan <zb(at)cybertec(dot)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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Leonardo F 2010-01-21 08:18:01 Re: About "Our CLUSTER implementation is pessimal" patch
Previous Message Takahiro Itagaki 2010-01-21 07:52:25 Re: Largeobject Access Controls (r2460)