From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nico Williams <nico(at)cryptonector(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fork()-safety, thread-safety |
Date: | 2017-10-06 01:19:54 |
Message-ID: | CAMsr+YHYJo9dNXYEhB_KycBzNWCS8CtUr2nu+pyPDZ0S4GJHvQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6 October 2017 at 08:06, Andres Freund <andres(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2017-10-06 01:29:31 | Re: Optimise default partition scanning while adding new partition |
Previous Message | Andres Freund | 2017-10-06 00:25:01 | Re: fork()-safety, thread-safety |