Path: utzoo!attcan!uunet!mailrus!cs.utexas.edu!samsung!aplcen!haven!vrdxhq!dev!dgis!jkrueger
From: jkrueger@dgis.dtic.dla.mil (Jon)
Newsgroups: comp.databases
Subject: Re: Lock problem on Ingres, Please help.
Keywords: Ingres
Message-ID: <770@dgis.dtic.dla.mil>
Date: 21 Feb 90 13:14:35 GMT
References: <673@modulex.dk> <1671@aurora.AthabascaU.CA> <9072@stiatl.UUCP>
Organization: Defense Technical Information Center (DTIC), Alexandria VA
Lines: 15

dmn@stiatl.UUCP (Michael Nowacki) writes:

>i am planning to create an SIR about this, proposing the option of record level
>locking be implemented in ingres.

Not clear this is a good thing; as you point out, one trades finer
granulariy of locking for throughput and possibly latency.  Concurrency
performance in general is quite hairy.  Consider other vendors' options
here and how configurable they are or are not.  It's a mixed bag.

-- Jon
-- 
Jonathan Krueger    jkrueger@dtic.dla.mil   uunet!dgis!jkrueger
The Philip Morris Companies, Inc: without question the strongest
and best argument for an anti-flag-waving amendment.