PostgreSQL and Windows2000 and defunct processes

From: Steven Vajdic <svajdic(at)asc(dot)corp(dot)mot(dot)com>
To: pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, svajdic(at)asc(dot)corp(dot)mot(dot)com, steven_vajdic(at)yahoo(dot)com(dot)au
Subject: PostgreSQL and Windows2000 and defunct processes
Date: 2002-06-06 06:53:29
Message-ID: 3CFF06E9.F3CA9622@asc.corp.mot.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Problem:

Win2000 and Cygwin/postgresql-7.1 produce
"defunct" processes after each run which can ONLY be killed
by Win Task Manager. If you allow too many "defunct" processes
your database requests slow down and your number of connections
increases, i.e. if you
have 32 connections specified in your postgresql.conf file and
and 32 "defunct" processes and try to run again
the connection will be refused.
When you are killing "defunct" processes and reach the one which was
first formed
the postmaster restarts postgresql.

How to get read of those "defunct" processes?

Much obliged.

Steven.

P.S. You do not have these "defunct" processes under Win98!!!???

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nicolas Nolst 2002-06-06 09:40:51 performance issue using DBI
Previous Message Wayne Stoker 2002-06-06 01:13:58 Duplicate definitions of _start and _fini and others when linking

Browse pgsql-hackers by date

  From Date Subject
Next Message ISHIKAWA Toshiyuki 2002-06-06 07:38:55 Re: Cooperation
Previous Message Tom Lane 2002-06-06 05:18:26 Straight-from-the-horses-mouth dept