Re: Postgres 16.1 - Bug: cache entry already complete

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Amadeo Gallardo <amadeo(at)ruddr(dot)io>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres 16.1 - Bug: cache entry already complete
Date: 2024-01-02 23:59:08
Message-ID: CAApHDvou8vFXVTbmnWZhetWsaQyXnaRNkJx49WrZEvz_TZ4cow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 3 Jan 2024 at 12:49, Amadeo Gallardo <amadeo(at)ruddr(dot)io> wrote:
> Attached is a sample script that I used to reproduce the error. I had to add some specific sample data and force-disable certain 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-01-03 00:05:30 Re: Postgres 16.1 - Bug: cache entry already complete
Previous Message Amadeo Gallardo 2024-01-02 23:48:58 Re: Postgres 16.1 - Bug: cache entry already complete