Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!bionet!ucselx!thompson
From: thompson@ucselx.sdsu.edu (thompson s)
Newsgroups: comp.databases
Subject: INGRES dead process/thread recovery
Message-ID: <1990Jul25.193815.7547@ucselx.sdsu.edu>
Date: 25 Jul 90 19:38:15 GMT
Reply-To: thompson@ucselx.sdsu.edu (thompson s)
Organization: San Diego State University Computing Services
Lines: 29

Has anyone out there using INGRES 6.nn (preferably) on a VMS based
VAX experienced the following problem?

	A user passes a query to the server (via ISQL) that is
	non-trivial (eg. based on a complex view, etc..) and 
	decides that s/he doesn't really want to run the query
        so s/he issues a <ctrl>C to abort the query...

	The server apparently gets passed the "interrupt" and
	puts the query's thread into a CS_DEAD_MASK state (this  
	was determined via IPM).  Meanwhile the server goes into
	a wild frenzy of disk thrashing (LOTS of DIO) and all other
	threads on the server get marginal (if that) response.

	The folks at INGRES seem to think that the server is doing
	some sort of necessary clean-up, but this lasts for hours
	and eventually we have to kill the server and start a new
	one...

Help me if you can...

I'll even accept sym/empathy!


					Bye Now,

					Scott Thompson
					San Diego State University
					(619) 594-4276