Re: An incorrect check in get_memoize_path

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
Cc: Andrei Lepikhov <lepihov(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: An incorrect check in get_memoize_path
Date: 2025-04-16 02:11:57
Message-ID: CAMbWs48zB_6T9XP=0U+Z_RmO-fPW1ecoU1xMCCCc91nkRAMj3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 14, 2025 at 8:08 PM wenhui qiu <qiuwenhuifx(at)gmail(dot)com> wrote:
> No objections.It's a pity that the postgresql18 version has been code-frozen

v18 is now in feature freeze, but not code freeze, so bug fixes are
still allowed. I've pushed this patch after adding the "Reviewed-by"
tags.

Thanks
Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhijie Hou (Fujitsu) 2025-04-16 02:52:29 RE: Skipping schema changes in publication
Previous Message Chapman Flack 2025-04-16 02:10:59 transforms [was Re: FmgrInfo allocation patterns (and PL handling as staged programming)]