Re: Postgres 16.1 - Bug: cache entry already complete - Mailing list pgsql-bugs

From David Rowley
Subject Re: Postgres 16.1 - Bug: cache entry already complete
Date
Msg-id CAApHDvou8vFXVTbmnWZhetWsaQyXnaRNkJx49WrZEvz_TZ4cow@mail.gmail.com
Whole thread Raw
In response to Postgres 16.1 - Bug: cache entry already complete  (Amadeo Gallardo <amadeo@ruddr.io>)
Responses Re: Postgres 16.1 - Bug: cache entry already complete  (Richard Guo <guofenglinux@gmail.com>)
List pgsql-bugs
On Wed, 3 Jan 2024 at 12:49, Amadeo Gallardo <amadeo@ruddr.io> wrote:
> Attached is a sample script that I used to reproduce the error. I had to add some specific sample data and
force-disablecertain planner settings, as otherwise the problem did not occur.
 
> Additionally, here's a trace of the error:

Thanks for the reproducer.  I can recreate this using your script
after adding an ANALYZE after the INSERTs. Without ndistinct
statistics, the planner won't risk using Memoize.

I'll investigate the cache complete error.

David



pgsql-bugs by date:

Previous
From: Amadeo Gallardo
Date:
Subject: Re: Postgres 16.1 - Bug: cache entry already complete
Next
From: Tom Lane
Date:
Subject: Re: Postgres 16.1 - Bug: cache entry already complete