Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 07:51:00 -0400 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: cygserver - Postgres hung Message-ID: <20040909115100.GA104216@tishler.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <008d01c495d8$877590c0$6401a8c0 AT EDJMETCALFE> <20040909011539 DOT GC101612 AT tishler DOT net> <20040909075916 DOT GB2953 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040909075916.GB2953@cygbert.vinschen.de> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Corinna, On Thu, Sep 09, 2004 at 09:59:16AM +0200, Corinna Vinschen wrote: > 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? I apologize for the terse, possibly misleading statement above. What I meant was there is nothing stopping one from building PostgreSQL against cygipc, but it won't be me. IMO, doing so is the wrong approach; fixing cygserver problems is the right approach. 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 -- 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/