Re: [HACKERS] Threads vs Processes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>
Cc: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: [HACKERS] Threads vs Processes
Date: 2003-09-25 17:03:02
Message-ID: 18576.1064509382@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-hackers-win32

Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> writes:
> One thing that can be done is to arrange all globals/statics in a
> structure and make that structure thread local.

That's about as far from "non-invasive" as I can imagine :-(

I really, really want to avoid doing anything like the above, because it
would force us to expose to the whole backend many data structures and
state variables that are currently local to individual .c files. That
complicates understanding and debugging tremendously, not to mention
slowing the edit/compile/debug cycle when you are changing such
structures.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message markw 2003-09-25 17:04:27 Re: Is this a commit problem?
Previous Message markw 2003-09-25 17:00:02 Re: Is this a commit problem?

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Cyrille Chepelov 2003-09-25 18:22:18 Re: [HACKERS] Threads vs Processes (was: NuSphere and PostgreSQL for
Previous Message Bruce Momjian 2003-09-25 16:57:09 Re: [HACKERS] Threads vs Processes (was: NuSphere and PostgreSQL for