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

From Matthias van de Meent
Subject Re: Let's make PostgreSQL multi-threaded
Date
Msg-id CAEze2WiNweEqUALCX2-Xb1m+XAakLBiBSztiTScv2OTw4DOW8Q@mail.gmail.com
Whole thread Raw
In response to Re: Let's make PostgreSQL multi-threaded  (Dave Cramer <davecramer@postgres.rocks>)
List pgsql-hackers
On Fri, 9 Jun 2023 at 17:20, Dave Cramer <davecramer@postgres.rocks> wrote:
>
> This is somewhat orthogonal to the topic of threading but relevant to the use of resources.
>
> If we are going to undertake some hard problems perhaps we should be looking at other problems that solve other long
termissues before we commit to spending resources on changing the process model.
 

-1. This and that are orthogonal and effort in one does not need to
block the other. If someone is willing to put in the effort, let them.
Last time I checked we, as a project, are not blocking bugfixes for
new features in MAIN either (or vice versa).

> One thing I can think of is upgrading. AFAIK dump and restore is the only way to change the on disk format.
> Presuming that eventually we will be forced to change the on disk format it would be nice to be able to do so in a
mannerwhich does not force long down times
 

I agree that we should improve our upgrade process (and we had a great
discussion on the topic at the PGCon Unconference last week), but in
my view that's not relevant to this discussion.

Kind regards,

Matthias van de Meent
Neon, Inc.



pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Let's make PostgreSQL multi-threaded
Next
From: Jeff Davis
Date:
Subject: Re: Order changes in PG16 since ICU introduction