Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!pacbell.com!ames!eos!shelby!portia.stanford.edu!chesky
From: chesky@portia.Stanford.EDU (Snehylata Gupta)
Newsgroups: comp.databases
Subject: Re: INGRES dead process/thread recovery
Message-ID: <1990Jul25.220115.14785@portia.Stanford.EDU>
Date: 25 Jul 90 22:01:15 GMT
References: <1990Jul25.193815.7547@ucselx.sdsu.edu>
Organization: AIR, Stanford University
Lines: 35

In article <1990Jul25.193815.7547@ucselx.sdsu.edu> thompson@ucselx.sdsu.edu (thompson s) writes:
>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

Deleted stuff

>	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!
>
>					Scott Thompson
The Ingres people are right.
We had the same problem running Ingres 6.3 on VMS 5.2 some one did a
select * from table_1 where key like %
and the table had 40,000 rows, after a while he did a cntrl - C.
We watched that process for 6 hours through IPM and when we were about
to kill the server it vanished. So in this case I agree with the INGRES
folks. One thing that you can do is as follows : Raise the base priority
of the process running that INGRES process. It should clean it up
faster. Because I think that INGRES processes inherit the base
priorities of the aprent process.

Otherwise there is nothing you can do except shut down that server.

You can bring up another server while the other one continues the
rollback process.

Sanjay