From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amadeo Gallardo <amadeo@ruddr.io>
cc: pgsql-bugs@lists.postgresql.org, David Rowley <dgrowleyml@gmail.com>
Subject: Re: Postgres 16.1 - Bug: cache entry already complete
In-reply-to: 
 <CADFREbW-BLJd7-a5J+5wjVumeFG1ByXiSOFzMtkmY_SDWckTxw@mail.gmail.com>
References: 
 <CADFREbW-BLJd7-a5J+5wjVumeFG1ByXiSOFzMtkmY_SDWckTxw@mail.gmail.com>
Comments: In-reply-to Amadeo Gallardo <amadeo@ruddr.io>
	message dated "Tue, 02 Jan 2024 12:36:11 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4103443.1704216682.1@sss.pgh.pa.us>
Date: Tue, 02 Jan 2024 12:31:22 -0500
Message-ID: <4103444.1704216682@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4103444.1704216682%40sss.pgh.pa.us>
Precedence: bulk

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