Re: lock_timeout GUC patch - Mailing list pgsql-hackers

From Boszormenyi Zoltan
Subject Re: lock_timeout GUC patch
Date
Msg-id 4B4D8EE4.8050805@cybertec.at
Whole thread Raw
In response to Re: lock_timeout GUC patch  (Jaime Casanova <jcasanov@systemguards.com.ec>)
Responses Re: lock_timeout GUC patch  (Jaime Casanova <jcasanov@systemguards.com.ec>)
List pgsql-hackers
Jaime Casanova írta:
> 2010/1/13 Boszormenyi Zoltan <zb@cybertec.at>:
>   
>> Tom Lane írta:
>>     
>>> If this patch is touching those parts of relcache.c, it probably needs
>>> rethinking.
>>>
>>>       
>> What I did there is to check the return value of LockRelationOid()
>>     
>
> the hunk was because a diference in the position (i guess patch accept
> a hunk of reasonable size, assuming there is something like a
> reasonable size for that)
>
> and is not touching the same as your refactor (sorry if i explain myself bad)
>
>   
>> and also elog(PANIC) if the lock wasn't available.
>> Does it need rethinking?
>>
>>     
>
> well, i actually think that PANIC is too high for this...
>   

Well, it tries to lock and then open a critical system index.
Failure to open it has PANIC, it seemed appropriate to use
the same error level if the lock failure case.

Best regards,
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: Fujii Masao
Date:
Subject: Re: Streaming replication and non-blocking I/O
Next
From: Zdenek Kotala
Date:
Subject: Deadlock in vacuum (check fails)