Re: Postgres/Cygwin - Semaphores

Lists: pgsql-cygwin
From: Saravanan Bellan <Saravanan(dot)Bellan(at)veritas(dot)com>
To: "'pgsql-cygwin(at)postgresql(dot)org'" <pgsql-cygwin(at)postgresql(dot)org>
Subject: Postgres/Cygwin - Semaphores
Date: 2003-04-08 04:16:58
Message-ID: C3CC003A39C7D411910F0008C786A645055F07AC@mtvxch12.veritas.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-cygwin

We use Tomcat(4.1) DBCP Connection pooling to access Postgres(7.2.1) on
Windows.
What we notice is that the number of handles used by the postmaster process
on the server
gradually increases if the same connection is used for update operations for
a extended period of time.
In a couple of days of high activity the number of handles is in the range
of 2 million and
eventually crashes the server.

You can see the number of handles in Windows Task manager. With the Process
Explorer tool
(www.sysinternals.com) you could see that these handles are all Semaphore
handles.

Running Vacuum at regular intervals helps to prolong the crash by some more
days.

Any suggestions,

Thanks,


From: Jason Tishler <jason(at)tishler(dot)net>
To: Saravanan Bellan <Saravanan(dot)Bellan(at)veritas(dot)com>
Cc: "'pgsql-cygwin(at)postgresql(dot)org'" <pgsql-cygwin(at)postgresql(dot)org>
Subject: Re: Postgres/Cygwin - Semaphores
Date: 2003-04-10 12:46:46
Message-ID: 20030410124646.GB1588@tishler.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-cygwin

On Mon, Apr 07, 2003 at 09:16:58PM -0700, Saravanan Bellan wrote:
> Any suggestions,

Debug? You probably found YA bug in cygipc. My suggestion is to build
a debug version of PostgreSQL against a debug version of cygipc and go
at it.

Another alternative is to help finish the SysV IPC in Cygwin so that we
can finally retire cygipc.

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6