X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5A783D1B53C for ; Thu, 25 Sep 2003 12:59:57 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 97776-09 for ; Thu, 25 Sep 2003 09:59:50 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 10D5DD1B537 for ; Thu, 25 Sep 2003 09:59:46 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h8PCxW6c001795; Thu, 25 Sep 2003 08:59:32 -0400 (EDT) To: Robert Treat Cc: Bruce Momjian , pgsql-hackers@postgreSQL.org Subject: Re: [pgsql-www] NuSphere and PostgreSQL for windows In-reply-to: <1064492591.25702.2084.camel@camel> References: <200309241711.h8OHBMi20283@candle.pha.pa.us> <1064492591.25702.2084.camel@camel> Comments: In-reply-to Robert Treat message dated "25 Sep 2003 08:23:11 -0400" Date: Thu, 25 Sep 2003 08:59:32 -0400 Message-ID: <1794.1064494772@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/1222 X-Sequence-Number: 44234 Robert Treat writes: > On Wed, 2003-09-24 at 13:11, Bruce Momjian wrote: >> SRA's Windows port is up to 7.3.4, and I think they just released >> version 1.1, so that is going fine --- and I have the source code to >> use in our native Win32 port, just not the threading stuff. > And if I've paid attention, the threading bits are what SRA used to get > around the fork/exec issues? BTW, I've been wondering lately if we'd not be better off to look at using threading in the Windows port, if it'd help us get around the fork/exec data transfer problem. I'm not sure that it would, mind you, but if it would give an answer it might be a lot less painful than solving the data transfer problem directly. Our main objections to threading in the past have always been lack of portability and loss of robustness. Portability isn't an issue for a Windows-only solution, and I'm not too concerned about the other either, since I'll never think that Windows would be a place to run a production server anyway. regards, tom lane