Re: "type with xxxx does not exist" when doing ExecMemoize() - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: "type with xxxx does not exist" when doing ExecMemoize()
Date
Msg-id abb6240f-4fa9-47a0-8b4d-89573ad957fc@postgrespro.ru
Whole thread Raw
In response to Re: "type with xxxx does not exist" when doing ExecMemoize()  (Tender Wang <tndrwang@gmail.com>)
Responses Re: "type with xxxx does not exist" when doing ExecMemoize()
List pgsql-hackers
On 28/2/2024 13:53, Tender Wang wrote:
> The attached patch is a new version based on v3(not including Andrei's 
> the test case). There is no need to call datumCopy when
> isnull is true.
> 
> I have not added a new runtime memoryContext so far. Continue to use 
> mstate->tableContext, I'm not sure the memory used of probeslot will 
> affect mstate->mem_limit.
> Maybe adding a new memoryContext is better. I think I should spend a 
> little time to learn nodeMemoize.c more deeply.
I am curious about your reasons to stay with tableContext. In terms of 
memory allocation, Richard's approach looks better.
Also, You don't need to initialize tts_values[i] at all if tts_isnull[i] 
set to true.

-- 
regards,
Andrei Lepikhov
Postgres Professional




pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Synchronizing slots from primary to standby
Next
From: Bertrand Drouvot
Date:
Subject: Re: Synchronizing slots from primary to standby