Re: Error code returned by lock_timeout - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Error code returned by lock_timeout
Date
Msg-id CAHGQGwHAom4SyODQ_Orkdc_V_KU=GiOt0mh=3K_bpmNxdySHGg@mail.gmail.com
Whole thread Raw
In response to Error code returned by lock_timeout  (Boszormenyi Zoltan <zb@cybertec.at>)
Responses Re: Error code returned by lock_timeout
List pgsql-hackers
On Thu, Jun 27, 2013 at 2:22 PM, Boszormenyi Zoltan <zb@cybertec.at> wrote:
> Hi,
>
> I just realized that in the original incarnation of lock_timeout,
> I used ERRCODE_LOCK_NOT_AVAILABLE (to be consistent with NOWAIT)
> but the patch that was accepted into 9.3 contained ERRCODE_QUERY_CANCELED
> which is the same as for statement_timeout.
>
> Which would be more correct?

ISTM that ERRCODE_LOCK_NOT_AVAILABLE is more suitable...

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add more regression tests for dbcommands
Next
From: Michael Meskes
Date:
Subject: Re: [9.3 doc fix] ECPG VAR command does not describe the actual specification