Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 9 Sep 2004 09:59:16 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: cygserver - Postgres hung Message-ID: <20040909075916.GB2953@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <008d01c495d8$877590c0$6401a8c0@EDJMETCALFE> <20040909011539.GC101612@tishler.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@cygwin.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/