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

From Craig Ringer
Subject Re: [HACKERS] fork()-safety, thread-safety
Date
Msg-id CAMsr+YHYJo9dNXYEhB_KycBzNWCS8CtUr2nu+pyPDZ0S4GJHvQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] fork()-safety, thread-safety  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 6 October 2017 at 08:06, Andres Freund <andres@anarazel.de> wrote:
> 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.

Yeah. We have a pretty major NIH problem in PostgreSQL, and I agree
that adopting threading and some commonplace tools would sure help us
reduce that burden a bit.

I would really miss shared-nothing-by-default though.

-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services


-- 
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: Amit Langote
Date:
Subject: Re: [HACKERS] Optimise default partition scanning while adding newpartition