* Postgres Pro Standard 9.5, 9.6;

* Postgres Pro Enterprise;

By the way, we have a growing Wiki[out there](https://github.com/postgrespro/pg_pathman/wiki).

Take a look at our Wiki[out there](https://github.com/postgrespro/pg_pathman/wiki).

**Partitioning** means splitting one large table into smaller pieces. Each row in such table is moved to a single partition according to the partitioning key. PostgreSQL supports partitioning via table inheritance: each partition must be created as a child table with CHECK CONSTRAINT. For example:

**Partitioning** means splitting one large table into smaller pieces. Each row in such table is moved to a single partition according to the partitioning key. PostgreSQL<= 10supports partitioning via table inheritance: each partition must be created as a child table with CHECK CONSTRAINT:

CREATETABLEtest (idSERIALPRIMARY KEY, titleTEXT);

CREATETABLEtest_1 (CHECK ( id>=100AND id<200 )) INHERITS (test);

CREATETABLEtest_2 (CHECK ( id>=200AND id<300 )) INHERITS (test);

PostgreSQL 10 provides native partitioning:

CREATETABLEtest(id int4, valuetext) PARTITION BY RANGE(id);

CREATETABLEtest_1 PARTITION OF test FORVALUESFROM (1) TO (10);

CREATETABLEtest_2 PARTITION OF test FORVALUESFROM (10) TO (20);

It's not so different from the classic approach; there are implicit check constraints, and most of its limitations are still relevant.

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. It stores partitioning configuration in the`pathman_config` table; each row contains a single entry for a partitioned table (relation name, partitioning column and its type). During the initialization stage the`pg_pathman` module caches some information about child partitions in the shared memory, which is used later for plan construction. Before a SELECT query is executed,`pg_pathman` traverses the condition tree in search of expressions like:

* FDW support (foreign partitions);

* Various GUC toggles and configurable settings.

* Multi-level partitioning (ver 1.5);

* Improved referential integrity + foreign keys on partitioned tables (ver 1.5);

Take a look at[this page](https://github.com/postgrespro/pg_pathman/wiki/Roadmap);

To install`pg_pathman`, execute this in the module's directory: