Horton

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

Masahiko Sawada <sawada.mshk@gmail.com>

View thread View on postgr.es
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Fujii Masao <masao.fujii@oss.nttdata.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-10T22:10:02Z
Lists: pgsql-hackers

Attachments

On Thu, Oct 10, 2024 at 8:26 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> On Thu, Oct 10, 2024 at 8:04 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
> >
> >
> >
> > 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?
> >
>
> Yes, I'll post the patch soon.
>

Please find the attached patches.

Regards,

-- 
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

Commits

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

  2. Generational memory allocator