Re: Curosity question regarding "LOCK" NOWAIT

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: David Johnston <polobo(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Curosity question regarding "LOCK" NOWAIT
Date: 2012-09-22 05:55:29
Message-ID: CAK3UJRG2pxqZ_LwM0uTVfOgYMM7R3xo1md7XDoFD7cTvyHY7Ew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Sep 21, 2012 at 7:43 PM, David Johnston <polobo(at)yahoo(dot)com> wrote:
> Has there been any discussion regarding adding a time-limited version of
> NOWAIT, say: “WAITONLY 50” (milliseconds), when dealing the explicit LOCK
> TABLE or the SELECT…FOR(SHARE|UPDATE) commands?

I think you could do this by issuing

SET statement_timeout = 50;

and then attempting the LOCK TABLE or SELECT ... FOR UPDATE command,
without NOWAIT. You'll either get an "ERROR: canceling statement due
to statement timeout" or the command should succeed.

Josh

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jasen Betts 2012-09-22 06:46:21 Re: pg_dump slow on windows
Previous Message Jasen Betts 2012-09-22 05:33:22 Re: On Ubuntu 12.04 i do have two psql one of those isn't working