Skip to content

feat: Add pg_partman 5.5.0 as a SQL-only extension (NO_BGW) - #83

Open
gauthamchandra wants to merge 1 commit into
electric-sql:REL_18_3-pglitefrom
gauthamchandra:gauthamchandra/pg_partman
Open

feat: Add pg_partman 5.5.0 as a SQL-only extension (NO_BGW)#83
gauthamchandra wants to merge 1 commit into
electric-sql:REL_18_3-pglitefrom
gauthamchandra:gauthamchandra/pg_partman

Conversation

@gauthamchandra

@gauthamchandra gauthamchandra commented Aug 16, 2026

Copy link
Copy Markdown

pg_partman is a fairly popular extension for managing partitions in postgres. I wanted to add support for it to be used in pglite.

pg_partman's core is pure SQL/PLpgSQL; the only C component is its background worker, which schedules run_maintenance() and cannot exist in single-process WASM. Upstream officially supports building without it via NO_BGW=1, so the extension is packaged SQL-only and maintenance is invoked by the embedding application instead.

The submodule is pinned at the v5.5.0 release tag. It is intentionally kept out of SUBDIRS so the recursive 'all' build never attempts to compile the background worker with emscripten; only the dist rule touches it.

pg_partman's core is pure SQL/PLpgSQL; the only C component is its
background worker, which schedules run_maintenance() and cannot exist
in single-process WASM. Upstream officially supports building without
it via NO_BGW=1, so the extension is packaged SQL-only and maintenance
is invoked by the embedding application instead.

The submodule is pinned at the v5.5.0 release tag. It is intentionally
kept out of SUBDIRS so the recursive 'all' build never attempts to
compile the background worker with emscripten; only the dist rule
touches it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant