Re: minor change for create_list_bounds()

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>
To: Zhihong Yu <zyu@yugabyte.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-06-29T23:41:01Z
Lists: pgsql-hackers
On Tue, Mar 08, 2022 at 11:05:10AM -0800, Zhihong Yu wrote:
> 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().

Given this change probably doesn't meaningfully impact performance or code
clarity, I'm personally -1 for this patch.  Is there another motivation
that I am missing?

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



Commits

  1. Small cleanup of create_list_bounds()

  2. Allow ordered partition scans in more cases