Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 9 Sep 2004 09:59:16 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygserver - Postgres hung
Message-ID: <20040909075916.GB2953@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <008d01c495d8$877590c0$6401a8c0 AT EDJMETCALFE> <20040909011539 DOT GC101612 AT tishler DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040909011539.GC101612@tishler.net>
User-Agent: Mutt/1.4.2i

On Sep  8 21:15, Jason Tishler wrote:
> On Wed, Sep 08, 2004 at 03:17:48PM -0400, Jean-Pierre Pelletier wrote:
> > Another option would be to force PostgreSQL 7.4.5 to use cygipc
> > (instead of cygserver) Is that possible?
> 
> Yes, you can always build from source yourself.

Yeah, sounds like a good plan.  Let's all together go back to using
cygipc instead of debugging and tracking down the problem.  It's so
much easier.  I'm just wondering why I should spend time debugging
the problem then?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/