Message-ID: <d3da9856-0394-48e6-9f41-543c589e9585@postgrespro.ru>
Date: Mon, 26 Feb 2024 09:52:59 +0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: "type with xxxx does not exist" when doing ExecMemoize()
Content-Language: en-US
To: Tender Wang <tndrwang@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: 
 <CAHewXNnT6N6UJkya0z-jLFzVxcwGfeRQSfhiwA+NyLg-x8iGew@mail.gmail.com>
From: Andrei Lepikhov <a.lepikhov@postgrespro.ru>
Organization: Postgres Professional
In-Reply-To: 
 <CAHewXNnT6N6UJkya0z-jLFzVxcwGfeRQSfhiwA+NyLg-x8iGew@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/d3da9856-0394-48e6-9f41-543c589e9585%40postgrespro.ru>
Precedence: bulk

On 25/2/2024 20:32, Tender Wang wrote:
> I think in prepare_probe_slot(), should called datumCopy as the attached 
> patch does.
> 
> Any thoughts? Thanks.
Thanks for the report.
I think it is better to invent a Runtime Memory Context; likewise, it is 
already designed in IndexScan and derivatives. Here, you just allocate 
the value in some upper memory context.
Also, I'm curious why such a trivial error hasn't been found for a long time

-- 
regards,
Andrei Lepikhov
Postgres Professional