Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <20040930140808.21013.qmail@web60302.mail.yahoo.com>
Date: Thu, 30 Sep 2004 07:08:07 -0700 (PDT)
From: Patrick Samson <p_samson AT yahoo DOT com>
Subject: Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl
To: cygwin AT cygwin DOT com
In-Reply-To: <20040930135635.8435.qmail@web60305.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Sigh,
Just after this post, I ran into the hang.
So pgAdmin II is no better, may be just a little
more difficult to fire the hang.

Still searching ...

--- Patrick Samson wrote:
> 
> > Special note for Postgresql users:
> > So far I can only reproduce this problem if these
> > 3 conditions are met:
> > - many connections (20, 25, 27) doing a simple
> > SELECT
> > - a script running SELECT, CREATE/DROP TABLE/INDEX
> > ...
> > - a pgAdmin III connected (but without activity)
> > (Postgresql version 7.3.6)
> 
> Doesn't fail by just changing pgAdmin III with
> pgAdmin II.
> What's the difference?
> III tries first to talk in protocol V3 with the PG
> backend. If the backend doesn't understand this
> version, which the case for v7.3.6,
> pgAdmin falls back to protocol V2 and things go on.
> We can see it in the PG log with:
>  FATAL:  unsupported frontend protocol
> 
> Does it mean that the backend did something wrong
> with the IPCs when refusing V3 ...?


__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/