Re: Threads vs Processes - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Threads vs Processes
Date
Msg-id 20030927131911.X15218-100000@houston.familyhealth.com.au
Whole thread Raw
In response to Re: Threads vs Processes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > We really don't need threads to replace existing functionality. That
> > would be dog work.
>
> No, that's not the point at all.  The problem we are facing at the
> moment with the Windows port is lack of fork(), which means there's
> no way for separate-subprocess backends to inherit variable values
> from the postmaster.  Bruce has been trying to fix that by having the
> subprocesses somehow reload or re-deduce all those variables; which
> is messy, bug-prone, and probably race-condition-prone too.  In a
> threaded implementation it would maybe be relatively easy to initialize
> a new thread's TLS by copying the postmaster thread's TLS, in which case
> a whole pile of as-yet-unwritten Windows-only code won't be needed.

Kepp in mind though all the cool things that could be done if we had
thread capabilities.  eg. evaluating different subexpressings on
fdifferent cpuis for the one query, etc.

Chris



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: pg_get_triggerdef pretty printing
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: 2-phase commit