Re: checking for a NULL date in a partitioned table kills performance - Mailing list pgsql-admin

From Scott Ribe
Subject Re: checking for a NULL date in a partitioned table kills performance
Date
Msg-id 1F2BA008-3732-4289-876A-EF6889474E08@elevated-dev.com
Whole thread Raw
In response to Re: checking for a NULL date in a partitioned table kills performance  (Doug Reynolds <mav@wastegate.net>)
Responses Re: checking for a NULL date in a partitioned table kills performance
Re: checking for a NULL date in a partitioned table kills performance
List pgsql-admin
> On Aug 23, 2024, at 5:39 AM, Doug Reynolds <mav@wastegate.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
COALESCEin 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'msure you're right that no index would help. No matter what, it seems that sequential scans of all partitions will be
requiredsince most rows have it null, and it's not even related to the partition key. 


pgsql-admin by date:

Previous
From: Sbob
Date:
Subject: Re: checking for a NULL date in a partitioned table kills performance
Next
From: Doug Reynolds
Date:
Subject: Re: checking for a NULL date in a partitioned table kills performance