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

From Andreas Karlsson
Subject Re: Let's make PostgreSQL multi-threaded
Date
Msg-id fb103da5-930b-f6cb-b6d2-ea77172c18b9@proxel.se
Whole thread Raw
In response to Re: Let's make PostgreSQL multi-threaded  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
On 6/14/23 09:01, Kyotaro Horiguchi wrote:
> At Wed, 14 Jun 2023 08:46:05 +0300, Konstantin Knizhnik <knizhnik@garret.ru> wrote in
>> But I do not think that it is somehow related with using threads
>> instead of process.
>> The question whether to use private or shared cache is not directly
>> related to threads vs. process choice.
> 
> Yeah, I unconsciously conflated the two things. We can use per-thread
> cache on multithreading.

For sure, and we can drop the cache when dropping the memory context. 
And in the first versions of an imagined threaded PostgreSQL I am sure 
that is how things will work.

Then later someone will have to investigate which caches are worth 
making shared and what the eviction/expiration strategy should be.

Andreas



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Let's make PostgreSQL multi-threaded
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_waldump: add test for coverage