Re: [PATCHES] NO WAIT ...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>
Cc: Rod Taylor <pg(at)rbt(dot)ca>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] NO WAIT ...
Date: 2004-02-19 16:01:48
Message-ID: 200402191601.i1JG1m820902@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zeugswetter Andreas SB SD wrote:
>
> > > The question is whether we should have a GUC variable to control no
> > > waiting on locks or add NO WAIT to specific SQL commands.
> > >
> > > Does anyone want to vote _against_ the GUC idea for nowait locking. (We
> > > already have two voting for such a variable.)
> >
> > I vote against. We got bit by both the regex and the autocommit GUC vars
> > and this is setting up to cause a similar headache with old code on new
> > platforms.
>
> I vote for the GUC. Imho it is not comparable to the "autocommit" case,
> since it does not change the way your appl needs to react (appl needs to
> react to deadlock already).
>
> I personally think a wait period in seconds would be more useful.
> Milli second timeouts tend to be misused with way too low values
> in this case, imho.

I understand, but GUC lost the vote. I have updated the TODO list to
indicate this. Tatsuo posted a patch to add NO WAIT to the LOCK
command, so we will see if we can get that into CVS.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2004-02-19 16:05:13 Re: [PATCHES] NO WAIT ...
Previous Message Tom Lane 2004-02-19 16:01:14 Re: OIDs, CTIDs, updateable cursors and friends