Message-ID: <e376087c-1525-418e-bd78-17b5266fb680@postgrespro.ru>
Date: Wed, 6 Mar 2024 10:37:11 +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>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 Richard Guo <guofenglinux@gmail.com>, David Rowley <dgrowleyml@gmail.com>
References: 
 <CAHewXNnT6N6UJkya0z-jLFzVxcwGfeRQSfhiwA+NyLg-x8iGew@mail.gmail.com>
 <d3da9856-0394-48e6-9f41-543c589e9585@postgrespro.ru>
 <CAHewXNm9KEn8CMOK4q0zutkX4BK8o754LgQbzYKgcj7_g1GgjQ@mail.gmail.com>
 <7a6a807c-193f-4333-937b-8211b1330579@postgrespro.ru>
 <CAMbWs481ZsCBi+63mRatE0VByijSFwhu=OBARFptM4rsza-2Yw@mail.gmail.com>
 <aacdf19f-778d-4a92-a2ba-2fa5f56401b4@postgrespro.ru>
 <CAHewXNknsjG6JoDM48FWyyiFesG=K18vJMOY_LzPBDNV7DvmuQ@mail.gmail.com>
 <abb6240f-4fa9-47a0-8b4d-89573ad957fc@postgrespro.ru>
 <CAHewXN=mzgHyFR2c0Z1hYAozYHWTdrEW90=oh0_Jn9kZVp6fYQ@mail.gmail.com>
 <CAHewXNkjBAPY8L+-yiLGOvee41A3aoHZArkcUm1OCtYhDp8eTQ@mail.gmail.com>
 <a4f29a6b-c21f-4b08-800f-d279d82b0864@postgrespro.ru>
 <CAHewXNkro3agi6LmaLmQhjqwyi8nzu-sEitnK7EW9z4_e=DLKQ@mail.gmail.com>
From: Andrei Lepikhov <a.lepikhov@postgrespro.ru>
Organization: Postgres Professional
In-Reply-To: 
 <CAHewXNkro3agi6LmaLmQhjqwyi8nzu-sEitnK7EW9z4_e=DLKQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/e376087c-1525-418e-bd78-17b5266fb680%40postgrespro.ru>
Precedence: bulk

On 6/3/2024 10:10, Tender Wang wrote:
> 
> 
> Andrei Lepikhov <a.lepikhov@postgrespro.ru 
> <mailto:a.lepikhov@postgrespro.ru>> 于2024年3月5日周二 17:36写道：
> 
>     On 1/3/2024 14:18, Tender Wang wrote:
>      > During debug, I learned that numeric_add doesn't have type check
>     like
>      > rangetype, so aboved query will not report "type with xxx does
>     not exist".
>      >
>      > And I realize that  the test case added by Andrei Lepikhov  in v3 is
>      > right. So in v6 patch I add Andrei Lepikhov's test case.  Thanks
>     a lot.
>      >
>      > Now I think the v6 version patch seems to be complete now.
>     I've passed through the patch, and it looks okay. Although I am afraid
>     of the same problems that future changes can cause and how to detect
>     them, it works correctly.
> 
> 
> Thanks for reviewing it, and I add it to commitfest 2024-07.
I think, it is a bug. Should it be fixed (and back-patched) earlier?

-- 
regards,
Andrei Lepikhov
Postgres Professional