Re: Let's make PostgreSQL multi-threaded - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Let's make PostgreSQL multi-threaded
Date
Msg-id CA+TgmoassRX3R_8=_ocVm=P1cpevpWOThB2egomZ4MbFK31aeg@mail.gmail.com
Whole thread Raw
In response to Let's make PostgreSQL multi-threaded  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Tue, Jun 6, 2023 at 2:51 PM Kirk Wolak <wolakk@gmail.com> wrote:
> I do wonder if we could add better threading within any given session/process to get a hybrid?
> [maybe this gets us closer to solving some of the problems incrementally?]

I don't think it helps much -- if anything, I think that would be more
complicated.

> If I could have anything (today)... I would prefer a Master-Master Implementation leveraging some
> of the ultra-fast server-server communication protocols to help sync things.  Then I wouldn't care.
> I could avoid the O/S  Overwhelm caused by excessive processes, via spinning up machines.
> [Unfortunately I know that PG leverages the filesystem cache, etc to such a degree that communicating
> from one master to another would require a really special architecture there.  And the N! communication lines].

I think there's plenty of interesting things to improve in this area,
but they're different things than what this thread is about.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Kirk Wolak
Date:
Subject: Re: Let's make PostgreSQL multi-threaded
Next
From: Cary Huang
Date:
Subject: Re: Mark a transaction uncommittable