On Wed, May 7, 2025 at 09:27:14AM +1200, David Rowley wrote: > On Wed, 7 May 2025 at 07:44, Bruce Momjian <br...@momjian.us> wrote: > > I think what you are saying is that this has to do with partition > > processing of joins, but not the pruning process. I don't think a > > non-partition joins are likely to hit 32 EquivalenceClasses. > > A query such as: SELECT * FROM table_with_lots_of_partitions ORDER BY > col; will plan much faster now. No joins there.
Ah, interesting. I am guessing the ORDER BY requires the EquivalenceClasses items. Applied patch attached. I don't think we can make more precise wording for this item. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.
diff --git a/doc/src/sgml/release-18.sgml b/doc/src/sgml/release-18.sgml index 3ff9d9830e9..80cf415bb76 100644 --- a/doc/src/sgml/release-18.sgml +++ b/doc/src/sgml/release-18.sgml @@ -397,7 +397,7 @@ Author: David Rowley <drow...@postgresql.org> <listitem> <para> -Improve the efficiency of joins involving partitions (Ashutosh Bapat, Yuya Watari, David Rowley) +Improve the efficiency of planning queries accessing many partitions (Ashutosh Bapat, Yuya Watari, David Rowley) <ulink url="&commit_baseurl;88f55bc97">§</ulink> <ulink url="&commit_baseurl;d69d45a5a">§</ulink> </para>
