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 15420aea-3ad8-466b-ba61-5f22ac3197a9@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

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




pgsql-hackers by date:

Previous
From: Mikael Sand
Date:
Subject: Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding'
Next
From: Mikael Sand
Date:
Subject: Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding'