Re: lock_timeout GUC patch - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: lock_timeout GUC patch
Date
Msg-id 3073cc9b1001130639j13a9f518ma44392a5cea1f751@mail.gmail.com
Whole thread Raw
In response to Re: lock_timeout GUC patch  (Boszormenyi Zoltan <zb@cybertec.at>)
List pgsql-hackers
2010/1/13 Boszormenyi Zoltan <zb@cybertec.at>:
>>
>> 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.
>

if you try to open a critical system index and it doesn't exist is
clearly a signal of corruption, if you can't lock it it's just a
concurrency issue... don't see why they both should have the same
level of message

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157


pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Bloom index
Next
From: Tom Lane
Date:
Subject: Re: lock_timeout GUC patch