pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Luis P Caamano <lcaamano@mindspring.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Can statement_timeout emulated NOWAIT?
Date: Tue, 16 Mar 2004 10:56:54 -0500 (EST)
Message-ID: <200403161556.i2GFusW22068@candle.pha.pa.us> (raw)
In-Reply-To: <DIEAJDKECNMGBBCLCGFFAEHPCGAA.lcaamano@mindspring.com>


Yes, I think these are all correct, except I am not positive FOR UPDATE
NOWAIT will be in 7.5 unless someone codes it.

---------------------------------------------------------------------------

Luis P Caamano wrote:
> 
> I've researched the recent discussions about statement_timeout
> and NOWAIT and I'd like to confirm my understanding of the
> situation before acting on it.  Please let me know if the
> following statements are true:
> 
> - LOCK TABLE ... NOWAIT has been checked in and will be available
>   in 7.5
> 
> - SELECT ... FOR UPDATE NOWAIT is in the TODO list (among other
>   NOWAIT commands) but it will also be available in 7.5
> 
> - Using "SET LOCAL statement_timeout=xxx" can be used before
>   "SELECT ... FOR UPDATE" to emulate NOWAIT when the select
>   is simple and involves a relatively small number of rows.
>   That is, the following:
> 
>     BEGIN;
>     SET LOCAL statement_timeout=3000;
>     SELECT ... FOR UPDATE; -- (1 row)
>     COMMIT;
> 
>   will be equivalent to:
> 
>     BEGIN;
>     SELECT ... FOR UPDATE NOWAIT;
>     COMMIT;
> 
> - The NOWAIT feature will be able to handle select-for-updates
>   that involve many rows better than statement_timeout because
>   it will track timeouts on a row by row basis, which eliminates
>   false positives.  That is, if the statement_timeout is too
>   short for the select, it might fail before finishing the select
>   instead of failing because of locked row.
> 
> - The error raised by statement_timeout and NOWAIT will be the
>   same.
> 
> Basically, I'd like to write low level code that implements
> NOWAIT in the application using statement_timeout.  Later on,
> 7.5, I'd be able to reimplement the low level functions using
> NOWAIT without having to change the higher level code.
> 
> Your thoughts and comments are appreciated.
> 
> Thanks
> 
> Luis P Caamano
> Atlanta, GA, USA
>     
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (4+ messages)  latest in thread

Message-ID: <200403161556.i2GFusW22068@candle.pha.pa.us>
Permalink:  ../200403161556.i2GFusW22068@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200403161556.i2GFusW22068@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: pgman@candle.pha.pa.us, lcaamano@mindspring.com
  Subject: Re: Can statement_timeout emulated NOWAIT?
  In-Reply-To: <200403161556.i2GFusW22068@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox