RE: Locking problem ... again
Posted in 2001
When the table is not locked exclusive, the data and each index row
(containing the updated column I think) must be locked. How many indexes on
this table and on what columns?
The 7k locks even with this table locked exclusive implies a foreign key
constraint involving this table and rows in another table(s) are locked.
Other respondents told you how identify the other table(s).
MW
-----Original Message-----
From: owner-informix-list@iiug.iiug.org
[mailto:owner-informix-list@iiug.iiug.org]On Behalf Of Brett Geer
Sent: Tuesday, February 06, 2001 10:43 PM
To: Andrew Hamm
Cc: informix-list@iiug.org
Subject: Re: Locking problem ... again
nopes
brett
Andrew Hamm wrote:
>
> Brett Geer wrote in message <95o4p6$d5q$1@news.xmission.com>...
> >
> >update cocinstn set ins_pub_company = 26 where ins_pub_company = 9> >
> >grabs 60K locks before I kill it... Even with the table locked exclusive
> >it grabbed 7K
> >
> Errr Emmmm - is there referential integrity out there causing the extra
> locks?
--
-----------------------------------------------------------------
Brett's 12th law of UNIX administration...
People tend not to react well when they lose control over their
computers. Typically, it brings out the worst in them ...
-----------------------------------------------------------------
Brett Geer - UNIX Admin/Analyst/Programmer - Intratex Holdings.
Tel. +27 31 717 4000 Direct. +27 31 717 4146
Fax. +27 31 717 4001
-----------------------------------------------------------------
The little voices are talking to me again, telling me to reach
for a keyboard and type rm -rf /*
last week they had me rm -rf `echo $MANPATH | sed 's/:/ /g'`
now I fear I have no answers
-----------------------------------------------------------------