Re: [HACKERS] PID of backend

From: Maarten Boekhold <boekhold(at)tibco(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, Dmitry Samersoff <dms(at)wplus(dot)net>, pgsql-hackers(at)postgreSQL(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Subject: Re: [HACKERS] PID of backend
Date: 1999-06-08 13:49:22
Message-ID: 375D1F62.6C50C373@tibco.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Meanwhile, I still say that getting rid of a backend via kill() is a
> dangerous and unnecessary "recovery" mechanism. What's wrong with
> just closing and reopening the connection instead?

I don't know about later versions of pgsql, but I've a 6.3.2 system running
on a production system, and every once in a while one of the
backends will go crazy and eat CPU. This system is on a web server, and processes
requests tru a CGI script. For the administrator (i.e. me), it is impossible
to close the CGI<-->backend connection (the backend will keep running after I kill
off the CGI script). Only thing that will get things back in order is to kill that
backend (which sometimes also requires me to restart the postmaster, probably
because of some shared mem corruption).

Maarten

ps. This system is not a priority for me, I', quote happy with how it's running,
so please don't tell me to upgrade or give me any other suggestions.

--

Maarten Boekhold, boekhold(at)tibco(dot)com
TIBCO Finance Technology Inc.
The Atrium
Strawinskylaan 3051
1077 ZX Amsterdam, The Netherlands
tel: +31 20 3012158, fax: +31 20 3012358
http://www.tibco.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 1999-06-08 13:53:01 I don't like LIKE
Previous Message Dmitry Samersoff 1999-06-08 10:51:10 Re: [HACKERS] Priorities for 6.6