Re: [HACKERS] fork()-safety, thread-safety - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] fork()-safety, thread-safety
Date
Msg-id 5872.1507248941@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] fork()-safety, thread-safety  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] fork()-safety, thread-safety
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2017-10-06 07:59:40 +0800, Craig Ringer wrote:
>> The only thing that gets me excited about a threaded postgres is the
>> ability to have a PL/Java, PL/Mono etc that don't suck. We could do
>> some really cool things that just aren't practical right now.

> Faster parallelism with a lot less reinventing the wheel. Easier backend
> / session separation. Shared caches.

What you guys are talking about here is a threaded backend, which is a
whole different matter from replacing the client-side threading that Nico
was looking at.  That would surely offer far higher rewards, but the costs
to get there are likewise orders of magnitude greater.
        regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] fork()-safety, thread-safety
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] fork()-safety, thread-safety