Re: Threaded PosgreSQL server - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Threaded PosgreSQL server
Date
Msg-id 24964.1013193916@sss.pgh.pa.us
Whole thread Raw
In response to Re: Threaded PosgreSQL server  (<mkscott@sacadia.com>)
List pgsql-hackers
<mkscott@sacadia.com> writes:
> On Fri, 8 Feb 2002, Tom Lane wrote:
>> I have a sneaking feeling that what you are going to come up with is a
>> multi-megabyte patch to convert CurrentMemoryContext into a non-global,
>> which will require changing the parameter list of damn near every
>> routine in the backend.

> While working with 7.0.2, I changed the call signature on only about 10
> functions.  In the MemoryContext example,
> MemorycontextSwitchTo(<Any>MemoryContext) turned into 
> MemoryContextSwitchTo(GetEnv()-><Any>MemoryContext).  You may be able 
> to do this with a #define.

Oh, I see.  Okay, if we can hide the messiness inside #define's then it
might not be as bad as I was expecting.  That'd also allow the overhead
to be compiled away when we didn't need/want thread support, which'd be
even nicer.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: compile error of PostgreSQL 7.2 on FreeBSD-current
Next
From: Vince Vielhaber
Date:
Subject: Re: PostgreSQL 7.2 on SlashDot