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 7691ED1B520 for ; Thu, 25 Sep 2003 14:07:56 +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 08438-01 for ; Thu, 25 Sep 2003 11:07:49 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 7E573D1B525 for ; Thu, 25 Sep 2003 11:07:45 -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 h8PE7e6c002795; Thu, 25 Sep 2003 10:07:40 -0400 (EDT) To: Andreas Pflug Cc: Bruce Momjian , pgsql-hackers@postgreSQL.org Subject: Re: NuSphere and PostgreSQL for windows In-reply-to: <3F72F033.30903@pse-consulting.de> References: <200309241711.h8OHBMi20283@candle.pha.pa.us> <1064492591.25702.2084.camel@camel> <1794.1064494772@sss.pgh.pa.us> <3F72F033.30903@pse-consulting.de> Comments: In-reply-to Andreas Pflug message dated "Thu, 25 Sep 2003 15:40:03 +0200" Date: Thu, 25 Sep 2003 10:07:39 -0400 Message-ID: <2794.1064498859@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/1227 X-Sequence-Number: 44239 Andreas Pflug writes: > Tom Lane wrote: >> 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. > When talking about threading in pgsql to Bruce on Linuxtag, he stated > that the main problem would be the tons of global variables used > throughout the backend. Yeah, it would reverse the problem from "how to share data" to "how not to share data". We'd want to find a way to ensure that the bulk of the static data becomes per-thread data (or, in some cases, add a mutex so that multiple threads can safely share one copy). It won't be a trivial bit of work, but conceivably it could be less messy than trying to store and reload many of those same variables. regards, tom lane