Re: pg12 - partition by column that might have null values
Michael Lewis <[email protected]> Thu, 3 Oct 2019 11:55:22 -0600
| Newsgroups | gmane.comp.db.postgresql.performance |
|---|---|
| Message-ID | <CAHOFxGrRE0DWbgGMteo4rM7RWoZqZ_JMxOk+a=aGALEKVdxY5w@mail.gmail.com> |
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?