| From: | Jelte Fennema <me(at)jeltef(dot)nl> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
| Subject: | Re: Support prepared statement invalidation when result types change |
| Date: | 2023-09-08 09:54:58 |
| Message-ID: | CAGECzQRAxPkgu=rnCA5YM=mF_MRSiyYH32vuW_TYdzuLcrcR4g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Another similar issue was reported on the PgBouncer prepared statement PR[1].
It's related to an issue that was already reported on the
mailinglist[2]. It turns out that invalidation of the argument types
is also important in some cases. The newly added 3rd patch in this
series addresses that issue.
[1]: https://github.com/pgbouncer/pgbouncer/pull/845#discussion_r1309454695
[2]: https://www.postgresql.org/message-id/flat/CA%2Bmi_8YAGf9qibDFTRNKgaTwaBa1OUcteKqLAxfMmKFbo3GHZg%40mail.gmail.com
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Support-prepared-statement-invalidation-when-resu.patch | application/x-patch | 7.3 KB |
| v3-0003-Support-changing-argument-types-of-prepared-state.patch | application/x-patch | 12.5 KB |
| v3-0002-Completely-remove-fixed_result-from-CachedPlanSou.patch | application/x-patch | 7.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2023-09-08 10:07:52 | Re: Using non-grouping-keys at HAVING clause |
| Previous Message | Ashutosh Bapat | 2023-09-08 09:52:33 | Reuse child_relids in try_partitionwise_join was Re: Assert failure on bms_equal(child_joinrel->relids, child_joinrelids) |