Re: Postgres 16.1 - Bug: cache entry already complete

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

Amadeo Gallardo <amadeo(at)ruddr(dot)io> writes:
> Upgrading from Postgres 14 to Postgres 16.1 introduced the following error
> when running a query:

> nativeError: error: select "date", coalesce(sum(hours), 0) as "hours" from
> "allocation_date" where "allocation_date"."project_id" = $1 and
> "allocation_date"."date" > $2 and "allocation_date"."hours" > $3 group by
> "date" order by "date" asc - cache entry already complete

> Note that `allocation_date` is a fairly complex view. Not quite sure what
> causes the "cache entry already complete", but it consistently failed in
> both the MacOS and Windows installations.

The only occurrence of that error string is in nodeMemoize.c, so
I suppose you've found a bug in Memoize. A bit odd that it doesn't
manifest in v14 where Memoize came in. But anyway, can you reduce
this to a self-contained test case?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message aa 2024-01-02 17:56:42 Re: Out of the box, full text search feature suggestion for postgresql
Previous Message Artur Zakirov 2024-01-02 17:20:51 Re: Out of the box, full text search feature suggestion for postgresql