Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower David Rowley <dgrowleyml@gmail.com> 10 июля 2023 г. в 02:14:04

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Richard Guo <guofenglinux@gmail.com> 10 июля 2023 г. в 06:39:27

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower David Rowley <dgrowleyml@gmail.com> 26 сентября 2023 г. в 13:42:32

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Richard Guo <guofenglinux@gmail.com> 28 сентября 2023 г. в 03:22:38

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower David Rowley <dgrowleyml@gmail.com> 28 сентября 2023 г. в 03:51:38

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Richard Guo <guofenglinux@gmail.com> 8 октября 2023 г. в 08:26:43

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Andrei Lepikhov <a.lepikhov@postgrespro.ru> 24 октября 2023 г. в 04:25:12

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Richard Guo <guofenglinux@gmail.com> 1 ноября 2023 г. в 02:20:49

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower David Rowley <dgrowleyml@gmail.com> 29 ноября 2023 г. в 00:48:10

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Richard Guo <guofenglinux@gmail.com> 1 декабря 2023 г. в 10:07:03

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Richard Guo <guofenglinux@gmail.com> 26 июля 2023 г. в 03:17:44

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower David Rowley <dgrowleyml@gmail.com> 7 июля 2022 г. в 00:46:17

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower "David G. Johnston" <david.g.johnston@gmail.com> 6 июля 2022 г. в 22:07:46

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Andres Freund <andres@anarazel.de> 7 июля 2022 г. в 00:46:46

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Tom Lane <tgl@sss.pgh.pa.us> 7 июля 2022 г. в 03:13:18

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Andres Freund <andres@anarazel.de> 7 июля 2022 г. в 04:36:56

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Tom Lane <tgl@sss.pgh.pa.us> 7 июля 2022 г. в 18:02:24

Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower David Rowley <dgrowleyml@gmail.com> 7 июля 2022 г. в 01:54:46

On Fri, 7 Jul 2023 at 19:03, Richard Guo  wrote:
> Attached is what I have in mind.  The patch extends the logic from two
> points.
>
> * it also checks OR clauses to see if it is always true.
>
> * it also checks for join clauses by additionally testing if the nulling
> bitmap is empty.

Do you mind writing some regression tests for this?

I don't really see an existing test file that would suit, maybe it's
worth adding something like predicate.sql

David

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

Предыдущее

От: Alexander Lakhin

Дата: 9 июля 2023 г. в 15:00:01

Сообщение: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger

Следующее

От: Richard Guo

Дата: 10 июля 2023 г. в 06:39:27

Сообщение: Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower