Re: checking for a NULL date in a partitioned table kills performance

The only difference is that you would be reading from one index instead of two, which could be more efficient.

Sent from my iPhone

> On Aug 23, 2024, at 11:19 AM, Scott Ribe <scott_ribe(at)elevated-dev(dot)com> wrote:
>
> 
>>
>> On Aug 23, 2024, at 5:39 AM, Doug Reynolds <mav(at)wastegate(dot)net> wrote:
>>
>> You could try something really ugly where you make a function index that COALESCEs the nulls to 1-1-1900 and use the COALESCE in the query.
>
> I don't see how that could be better than just creating a partial index on it WHERE contract_date IS NULL--and anyway I'm sure you're right that no index would help. No matter what, it seems that sequential scans of all partitions will be required since most rows have it null, and it's not even related to the partition key.
>