Re: ResultCache cache error: "cache entry already complete" in 14beta1 - Mailing list pgsql-bugs

From David Rowley
Subject Re: ResultCache cache error: "cache entry already complete" in 14beta1
Date
Msg-id CAApHDvrWsfc3naVQZxS0efU=vJOA7dG3NV7fGhkgo2=J38OEpg@mail.gmail.com
Whole thread Raw
In response to Re: ResultCache cache error: "cache entry already complete" in 14beta1  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: ResultCache cache error: "cache entry already complete" in 14beta1  (David Christensen <david.christensen@crunchydata.com>)
List pgsql-bugs
On Fri, 21 May 2021 at 11:05, David Rowley <dgrowleyml@gmail.com> wrote:
> I'll need to take a bit more time to check if that's a safe way to
> check if the entire join clause is parameterized or not.

I think it's fine to check the list_length() to see if any quals are
missing from the param info. This is very similar to what's done
already in generate_mergejoin_paths() to check if any join quals are
missing from the merge quals.

I've attached a cleaned-up patch.

David

Attachment

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: ResultCache cache error: "cache entry already complete" in 14beta1
Next
From: Robins Tharakan
Date:
Subject: Re: BUG #17022: SQL causing engine crash