pg_partman mit Homebrew, apt, dnf installieren

Projektlinks

• Homepage
• Paketmanager-Seite

Befehle und Aliase

• check_unique_constraint.py
• dump_partition.py
• vacuum_maintenance.py

Projektgeschichte

pg_partman began as a PostgreSQL extension for managing time- and number-based partition sets, including the trigger-based techniques required by older PostgreSQL releases. As PostgreSQL's declarative partitioning matured, pg_partman added support for the core implementation and migration tooling.

The 5.x series completed a major architectural transition: version 5.0.1 dropped trigger-based partitioning, required PostgreSQL 14 or newer, and standardized on built-in declarative partitioning. Later 5.x releases expanded supported partitioning forms and maintenance capabilities.

Adoptionsgeschichte

pg_partman is distributed not only from source but through community-maintained PostgreSQL operating-system packages. Its usefulness grew as PostgreSQL installations needed repeatable automation for creating future partitions, applying retention, and maintaining large time-series or sequence-based tables.

Wie es verwendet wird

Administrators create the extension in a chosen database schema, register existing declaratively partitioned parent tables, and configure policies in pg_partman's database configuration tables. Maintenance can be invoked by a scheduler or automated with the bundled background worker; retention, premaking, migration, and monitoring features support production partition lifecycles.

Warum Paket-Nerds sich dafür interessieren

The extension packages a substantial amount of PostgreSQL partitioning operational knowledge into database objects and an optional background worker. Package maintainers must track both PostgreSQL-version compatibility and major pg_partman migrations, particularly the transition away from trigger-based partitioning.

Zeitleiste

• Pre-5.0: pg_partman supported older trigger-based partitioning alongside PostgreSQL declarative partitioning.
• 2023: The 4.7 series added compatibility with PostgreSQL 16.
• 2024: Version 5.0.1 removed trigger-based partitioning and required PostgreSQL 14 or newer.
• 2025: The 5.x documentation described list partitioning and experimental numeric partitioning support.

Related projects

• PostgreSQL
• pg_jobmon
• pgTAP

Quellen

• https://github.com/pgpartman/pg_partman
• https://github.com/pgpartman/pg_partman/blob/development/CHANGELOG-pre-5.0.0.txt
• https://github.com/pgpartman/pg_partman/blob/development/CHANGELOG.md
• https://github.com/pgpartman/pg_partman/blob/development/doc/pg_partman.md