Re: Unexpected (wrong?) result querying boolean partitioned table with NULL partition - Mailing list pgsql-hackers

From David Kimura
Subject Re: Unexpected (wrong?) result querying boolean partitioned table with NULL partition
Date
Msg-id CAHnPFjRLQEmfM2vdCjGjLfGcPT6nt4j5Dspk3mqNtMqY1Stm-Q@mail.gmail.com
Whole thread Raw
In response to Re: Unexpected (wrong?) result querying boolean partitioned table with NULL partition  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
On Wed, Apr 12, 2023 at 4:13 AM David Rowley <dgrowleyml@gmail.com> wrote:
>
> There seems to be a bunch of tests checking this already, all of them
> assuming the incorrect plans.

Given that the plan alone wasn't sufficient to catch this error previously,
would it be worthwhile to add some data to the tests to make it abundantly
obvious?

I had noticed that the default partition seems to be an edge case in the code.
Perhaps it's overkill, but would it be worth adding a test where the NULL
partition is not the default?

Thanks,
David



pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: Should we remove vacuum_defer_cleanup_age?
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Add `verify-system` sslmode to use system CA pool for server cert