| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, william(dot)duclot(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower |
| Date: | 2023-07-10 02:14:04 |
| Message-ID: | CAApHDvr+70jEZpraMZ8sj=UH77dBzCaeUc9EcJHB3YaxX9syNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Fri, 7 Jul 2023 at 19:03, Richard Guo <guofenglinux(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2023-07-10 06:39:27 | Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower |
| Previous Message | Alexander Lakhin | 2023-07-09 15:00:01 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2023-07-10 02:24:43 | Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table. |
| Previous Message | Japin Li | 2023-07-10 01:04:42 | Re: Add hint message for check_log_destination() |