Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] 'Waiting on lock'

From: "Jaime Casanova" <systemguards(at)gmail(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] 'Waiting on lock'
Date: 2007-09-23 04:49:28
Message-ID: c2d9e70e0709222149y587a2317qfcaa3aeb88d5cf8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-patches
On 6/19/07, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> related TODO items:
> - add a WAIT n clause in same SQL locations as NOWAIT
> - add a lock_wait_timeout (USERSET), default = 0 (unlimited waiting)
>
> to provide better control over lock waits.
>

are these actual TODO items? i can't find them on the TODO list and i
don't remember any discussion nor patch about this

-- 
regards,
Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
                                       Richard Cook

In response to

Responses

pgsql-patches by date

Next:From: Gregory StarkDate: 2007-09-23 12:44:04
Subject: Re: [PATCHES] Eliminate more detoast copies for packed varlenas
Previous:From: Tom LaneDate: 2007-09-22 23:45:24
Subject: Re: Text <-> C string

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group