Handle pg_partman extension relations by catalog by cursor[bot] · Pull Request #16 · planetscale/heroku-migrator

cursor · 2026-06-29T22:17:20Z

Summary

Detect pg_partman through pg_extension instead of hard-coded schema names
Recreate pg_partman maintenance metadata for default/public extension installs
Exclude pg_partman extension-owned config tables and configured template tables from Bucardo relation registration
Keep application partition leaf tables replicated

bash -n scripts/mk-bucardo-repl.sh
bash -n test/test_pg_partman_setup.sh
bash test/test_pg_partman_setup.sh
bash -n test/test_e2e.sh
bash -n test/test_cutover.sh
ruby -c test/test_server_wrapper.rb
Local Postgres/pg_partman catalog integration with fake Bucardo verified metadata recreation and no part_config/template Bucardo registration

Full disposable-infrastructure validation was blocked in this VM because the Heroku/PlanetScale CLIs and required secret env vars were unavailable.

Based on: #10 (needed to make some changes to handle edge cases from some other recent improvements)

Co-authored-by: mike <mike@planetscale.com>

mscoutermarsh and others added 2 commits June 29, 2026 17:57

pg partman support

cf9fb8f

Based on: #10 (needed to make some changes to handle edge cases from some other recent improvements)

Handle pg_partman extension relations by catalog

2701c48

Co-authored-by: mike <mike@planetscale.com>