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
Date: Tue, 02 Jan 2024 12:31:22 -0500
Message-ID: <4103444.1704216682@sss.pgh.pa.us> (raw)
In-Reply-To: <CADFREbW-BLJd7-a5J+5wjVumeFG1ByXiSOFzMtkmY_SDWckTxw@mail.gmail.com>
References: <CADFREbW-BLJd7-a5J+5wjVumeFG1ByXiSOFzMtkmY_SDWckTxw@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, amadeo@ruddr.io, dgrowleyml@gmail.com
Subject: Re: Postgres 16.1 - Bug: cache entry already complete
In-Reply-To: <4103444.1704216682@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox