Re: ResultCache cache error: "cache entry already complete" in 14beta1

Поиск
Список
Период
Сортировка
От David Christensen
Тема Re: ResultCache cache error: "cache entry already complete" in 14beta1
Дата
Msg-id CAOxo6XKDDMwBV3co69s_DEfRTXCPqnvkO-sNOR3xV9W19TkzEw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: ResultCache cache error: "cache entry already complete" in 14beta1  (David Rowley <dgrowleyml@gmail.com>)
Ответы Re: ResultCache cache error: "cache entry already complete" in 14beta1  (David Rowley <dgrowleyml@gmail.com>)
Список pgsql-bugs
Дерево обсуждения
On Thu, May 20, 2021 at 6:35 PM David Rowley <dgrowleyml@gmail.com> wrote:
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.

I can confirm that this fixes the issue in our case (both in the actual query and in the minimal reproduction case).

Thanks!
 

В списке pgsql-bugs по дате отправления:

Предыдущее
От: david@pavlotzky.nl
Дата:
Сообщение: Re: BUG #17016: Cannot sync pgdg-common repo with reposync due to failed signature check
Следующее
От: Yuri Astrakhan
Дата:
Сообщение: Re: BUG #16076: JIT causes huge delays in a complex query. jit=off solves it.