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

From Tom Lane
Subject Re: Postgres 16.1 - Bug: cache entry already complete
Date
Msg-id 4103444.1704216682@sss.pgh.pa.us
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  (Amadeo Gallardo <amadeo@ruddr.io>)
List pgsql-bugs
Amadeo Gallardo <amadeo@ruddr.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



pgsql-bugs by date:

Previous
From: Artur Zakirov
Date:
Subject: Re: Out of the box, full text search feature suggestion for postgresql
Next
From: aa
Date:
Subject: Re: Out of the box, full text search feature suggestion for postgresql