Re: Let's make PostgreSQL multi-threaded

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
Subject: Re: Let's make PostgreSQL multi-threaded
Date: 2023-06-05 16:42:06
Message-ID: ZH4QXnfZH6WfCo6W@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 5, 2023 at 01:26:00PM -0300, Ranier Vilela wrote:
> On 05/06/2023 11:18, Tom Lane wrote:
> > For the record, I think this will be a disaster. There is far too much
> > code that will get broken, largely silently, and much of it is not
> > under our control.
>
> I fully agreed with Tom.
>
> First, it is not clear what are the benefits of architecture change?
>
> Performance?
>
> Development becomes much more complicated and error-prone.

I agree the costs of going threaded have been reduced with compiler and
library improvements, but I don't know if they are reduced enough for
the change to be a net benefit, except on Windows where the process
creation overhead is high.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Verite 2023-06-05 16:55:56 Simplify pg_collation.collversion for Windows libc
Previous Message 蔡梦娟 (玊于) 2023-06-05 16:39:47 回复:Fix missing initialization of delayChkptEnd