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>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, 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-10T15:04:31Z
Lists: pgsql-hackers 

On 2024/10/04 3:32, Masahiko Sawada wrote:
> Yes, but as for this macro specifically, I thought that it might be
> better to keep it, since it avoids breaking extension unnecessarily
> and it seems to be natural to have it as an option for slab context.

If the macro has value, I'm okay with leaving it as is.

Are you planning to post the patch?

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