Re: pg12 - partition by column that might have null values - Mailing list pgsql-performance

From Michael Lewis
Subject Re: pg12 - partition by column that might have null values
Date
Msg-id CAHOFxGrRE0DWbgGMteo4rM7RWoZqZ_JMxOk+a=aGALEKVdxY5w@mail.gmail.com
Whole thread Raw
In response to Re: pg12 - partition by column that might have null values  (Mariel Cherkassky <mariel.cherkassky@gmail.com>)
List pgsql-performance
Just create a partial index on id column where end_date = infinity (or null if you really prefer that pattern) and the system can quickly find the rows that are still most current revision. How many rows do you have in this table? Or foresee ever having? What took you down the road of partitioning the table? Theory only, or solving a real life optimization problem?

pgsql-performance by date:

Previous
From: Mariel Cherkassky
Date:
Subject: Re: pg12 - partition by column that might have null values
Next
From: Ogden Brash
Date:
Subject: Some observations on very slow pg_restore operations