Horton

Re: Using per-transaction memory contexts for storing decoded tuples

Fujii Masao <masao.fujii@oss.nttdata.com>

View thread View on postgr.es
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Shlok Kyal <shlok.kyal.oss@gmail.com>, David Rowley <dgrowleyml@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-10-03T09:46:25Z
Lists: pgsql-hackers 

On 2024/10/03 13:47, Masahiko Sawada wrote:
>>> I agree that the overhead will be much less visible in real workloads.
>>> +1 to use a smaller block (i.e. 8kB).

+1


>>> It's easy to backpatch to old
>>> branches (if we agree)

+1


>> It seems that
>> only reorderbuffer.c uses the LARGE macro so that it can be removed.
> 
> I'm going to keep the LARGE macro since extensions might be using it.

Yes, for the back-patch. But in the master branch,
we basically don't need to maintain this kind of compatibility?

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Commits

  1. Reduce memory block size for decoded tuple storage to 8kB.

  2. Generational memory allocator