HP3000-L Archives

June 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
john edwards <[log in to unmask]>
Reply To:
john edwards <[log in to unmask]>
Date:
Mon, 14 Jun 1999 05:41:52 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
Hi All
I've been reading the release 6 Turbo Image enhancements and see that
HP have at long last introduced a deadlock detection trap for the
DBLOCK intrinsic. It has been bundled with the multiple DB transaction
options.

I wonder if any of you know....

1) What performance overheads are involved?

2) Does it work with only one DB or multiple DBs?
example 1)
Step 1 - Process 1 Locks DB1 set1 unconditional - lock ok
Step 2 - Process 2 locks DB1 set2 unconditional - lock ok

Step 3 - Process 1 locks DB1 set2 unconditional - Deadlock detected?

example 2)
Step 1 - Process 1 Locks DB1 set1 unconditional - lock ok
Step 2 - Process 2 locks DB2 set2 unconditional - lock ok

Step 3 - Process 1 locks DB2 set2 unconditional - Deadlock detected?


Wish HP had introduced this years ago

Regards
John



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

ATOM RSS1 RSS2