From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: NuSphere and PostgreSQL for windows |
Date: | 2003-09-25 14:07:39 |
Message-ID: | 2794.1064498859@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Andreas Pflug <pgadmin(at)pse-consulting(dot)de> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Natoli | 2003-09-25 14:12:32 | Threads vs Processes (was: NuSphere and PostgreSQL for windows) |
Previous Message | Tom Lane | 2003-09-25 14:01:50 | Re: [pgsql-www] NuSphere and PostgreSQL for windows |
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-09-25 14:14:50 | Re: [pgsql-www] NuSphere and PostgreSQL for windows |
Previous Message | Tom Lane | 2003-09-25 14:01:50 | Re: [pgsql-www] NuSphere and PostgreSQL for windows |