Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!mips!prls!pyramid!infmx!aland From: aland@infmx.UUCP (Dr. Scump) Newsgroups: comp.databases Subject: Re: Informix locks on resources Summary: shared-memory SE issues are not related to Turbo Keywords: informix lock Message-ID: <3666@infmx.UUCP> Date: 21 Mar 90 10:13:20 GMT References: <647@gtenmc.UUCP> <370@mtndew.UUCP> <2314@promark.UUCP> Reply-To: aland@infmx.UUCP (alan denney) Organization: INFORMIX Professional Services ("Peace thru Normalization") Lines: 56 The following commentary is my own and in no way represents any official opinion of Informix. >In article <370@mtndew.UUCP>, friedl@mtndew.UUCP (Steve Friedl) writes: >> >> Oh boy. Turbo uses a shared-memory interface that lets all the >> various processes talk to each other, and it is remarkably >> easy for a process to go away and leave things locked. We use >> ISQL on the 3B15 with a similar shared-memory setup and we have >> no end of problems with it. Steve, I think that you are mixing two completely separate issues here. The original poster had asked about Informix-Turbo. The "similar shared- memory setup" that you refer to here has to do with the shared memory version of the standard engine (SE), which is a *completely* different animal. Also, if I remember right from prior conversations, you were working with shared memory SE as early as the 2.00.03/5 releases, which did have acknowledged problems in the 3B15-specific assembler code. Are the problems that you refer to present in the most recent version (2.10.03K on the 3B15, I think) ? In any event, those particular problems with locks on detaching processes did not apply to Turbo. In article <2314@promark.UUCP> mark@promark.UUCP (Mark J. DeFilippis) writes: >Oh boy is right. I just took a new job where I will be doing much coding >in C and ISQL. I worked extensively with the product for about 2.5 years over >2 years ago. Lots of problems. Interesting how some things never change. >When my new employer said they were having a hard time getting people who >know UNIX, C and ISQL, I think he meant "getting people who WILL WORK IN >ISQL". >-- >Mark J. DeFilippis begin flame; Jeez. "Lots of problems" in ISQL. O.K., whatever you say. In any event, if you want to post random flames about a company, fine, this is a public forum. However, to submit such a response to a sincere question a user had about a particular product (Turbo) with which you have no experience (as you stated to me in a phone conversation during the time you were working with ISQL 2 years ago) is, in my opinion, irresponsible. If you have since worked with Turbo and encountered genuine bugs in it, I apologize in advance. commit flame; >UUCP: philabs!sbcs!bnlux0!adelphi!markd -- Alan S. Denney @ Informix Software, Inc. "We're homeward bound aland@informix.com {pyramid|uunet}!infmx!aland ('tis a damn fine sound!) ----------------------------------------------- with a good ship, taut & free Disclaimer: These opinions are mine alone. We don't give a damn, If I am caught or killed, the secretary when we drink our rum will disavow any knowledge of my actions. with the girls of old Maui."