RE: AW: AW: timeout on lock feature - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: AW: AW: timeout on lock feature
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D33AC@sectorbase1.sectorbase.com
Whole thread Raw
In response to AW: AW: timeout on lock feature  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
> > The timeout will be useful to let the client or user decide
> > on an alternate course of action other that killing his
> > application (without the need for timers or threads in the
> > client program).
> 
> This assumes (without evidence) that the client has a good
> idea of what the timeout limit ought to be. I think this "feature"
> has no real use other than encouraging application programmers to
> shoot themselves in the foot. I see no reason that we should make
> it easy to misdesign applications.

AFAIR, Big Boys have this feature. If its implementation is safe,
ie will not affect applications not using it, why do not implement it?

Vadim


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Real/effective user
Next
From: Tom Lane
Date:
Subject: Re: Re: [PATCHES] Patch for PostgreSQL 7.0.3 to compile on Tru64 UNIX v5.0A