Postgres Pro
Downloads
Home   >   mailing lists

Re: Using per-transaction memory contexts for storing decoded tuples - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Using per-transaction memory contexts for storing decoded tuples
Date
Msg-id 9409d59d-808f-4c50-a7fc-6cdcc7d5674e@oss.nttdata.com
Whole thread Raw
In response to Re: Using per-transaction memory contexts for storing decoded tuples  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Using per-transaction memory contexts for storing decoded tuples
List pgsql-hackers
Tree view 

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

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Add on_error and log_verbosity options to file_fdw
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Check for TupleTableSlot nullness before dereferencing