On Thu, Mar 7, 2024 at 10:42 AM Benoit Tigeot <benoit.tig...@gmail.com> wrote: > I am not up to date with the last version of patch but I did a regular > benchmark with version 11 and typical issue we have at the moment and the > result are still very very good. [1]
Thanks for providing the test case. It was definitely important back when the ideas behind the patch had not yet fully developed. It helped me to realize that my thinking around non-required arrays (meaning arrays that cannot reposition the scan, and just filter out non-matching tuples) was still sloppy. > In term of performance improvement the last proposals could be a real game > changer for 2 of our biggest databases. We hope that Postgres 17 will contain > those improvements. Current plan is to commit this patch in the next couple of weeks, ahead of Postgres 17 feature freeze. -- Peter Geoghegan
