Re: Error code returned by lock_timeout

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, Hans-Jürgen Schönig <hs(at)cybertec(dot)at>
Subject: Re: Error code returned by lock_timeout
Date: 2013-06-27 15:03:53
Message-ID: CAHGQGwHAom4SyODQ_Orkdc_V_KU=GiOt0mh=3K_bpmNxdySHGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 27, 2013 at 2:22 PM, Boszormenyi Zoltan <zb(at)cybertec(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2013-06-27 15:07:47 Re: [9.3 doc fix] ECPG VAR command does not describe the actual specification
Previous Message Tom Lane 2013-06-27 14:57:24 Re: Add more regression tests for dbcommands