On Thu, Feb 8, 2018 at 4:51 PM, Ildar Musin <i.mu...@postgrespro.ru> wrote: > > The idea is to store min and max values of secondary attributes (like > 'id' in the example above) for each partition somewhere in catalog and > use it for partition pruning along with partitioning key.
Every insertion and update of secondary attribute will touch catalog and update if required. That will increase the contention on catalog. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
