Re: Support prepared statement invalidation when result types change - Mailing list pgsql-hackers

From Jelte Fennema
Subject Re: Support prepared statement invalidation when result types change
Date
Msg-id CAGECzQRAxPkgu=rnCA5YM=mF_MRSiyYH32vuW_TYdzuLcrcR4g@mail.gmail.com
Whole thread Raw
In response to Re: Support prepared statement invalidation when result types change  (Jelte Fennema <me@jeltef.nl>)
Responses Re: Support prepared statement invalidation when result types change
List 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

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Reuse child_relids in try_partitionwise_join was Re: Assert failure on bms_equal(child_joinrel->relids, child_joinrelids)
Next
From: Vik Fearing
Date:
Subject: Re: Using non-grouping-keys at HAVING clause