While 100 millions rows is not exactly big number for PostgreSQL, so you might be well without partitioning, but still. > Despite the flexibility, this approac

While 100 millions rows is not exactly big number for PostgreSQL, so you might be well without partitioning, but still. > Despite the flexibility, this approach forces the planner to perform an exhaustive search and to check constraints on each partition to determine whether it should be present in the plan or not. Large amount of partitions may result in significant planning overhead. > The pg_pathman module features partition managing functions and optimized planning mechanism which utilizes knowledge of the partitions' structure. https://github.com/postgrespro/pg_pathman https://github.com/postgrespro/pg_pathman