Re: assertion failure at cost_memoize_rescan()

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Kohei KaiGai <kaigai(at)heterodb(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: assertion failure at cost_memoize_rescan()
Date: 2024-06-18 22:23:23
Message-ID: CAApHDvp_Fc_DFx5dzA8P6P3dCXTfeujxwBBfdXqJ7Bkcz3rX5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 18 Jun 2024 at 15:14, Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
>
> On Tue, Jun 18, 2024 at 10:53 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> > I think the best solution is to apply the attached. I didn't test,
> > but it should fix the issue you reported and also ensure that
> > MemoizePath.calls is never zero, which would also cause issues in the
> > hit_ratio calculation in cost_memoize_rescan().
>
> +1.

Thanks for looking. Pushed.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas 'ads' Scherbaum 2024-06-18 22:40:52 Re: Proposal: Document ABI Compatibility
Previous Message Tomas Vondra 2024-06-18 22:02:56 Re: BitmapHeapScan streaming read user and prelim refactoring