minor change for create_list_bounds()
Zhihong Yu <zyu@yugabyte.com>
From: Zhihong Yu <zyu@yugabyte.com>
To: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-08T19:05:10Z
Lists: pgsql-hackers
Attachments
- list-bound-accepts-null.patch (application/octet-stream) patch
Hi, I was looking at commit db632fbca and noticed that, in create_list_bounds(), if index is added to boundinfo->interleaved_parts in the first if statement, there is no need to perform the second check involving call to partition_bound_accepts_nulls(). Here is a short patch. Cheers
Commits
-
Small cleanup of create_list_bounds()
- 559ec79e320e 15.0 landed
- f29199d3190f 16.0 landed
-
Allow ordered partition scans in more cases
- db632fbca392 15.0 cited