dbwarden-pgsql-extensions
PostgreSQL extension management for dbwarden.
Declare extensions in database_config(pg_extensions=[...]) and this plugin emits CREATE EXTENSION / DROP EXTENSION in the migration preamble, before any table that depends on them.
Object types
| Object type | Manages |
|---|---|
pg_extension |
CREATE EXTENSION IF NOT EXISTS / DROP EXTENSION IF EXISTS |
event_trigger |
CREATE EVENT TRIGGER / DROP EVENT TRIGGER |
extended_statistics |
CREATE STATISTICS / DROP STATISTICS for extended statistics objects |
function |
CREATE FUNCTION / DROP FUNCTION, including argument types for overload resolution |
trigger |
CREATE TRIGGER / DROP TRIGGER on tables |
storage_params |
Table storage parameters (fillfactor, autovacuum settings, and friends) |
Extension handlers run in RunPhase.PREAMBLE, anchored after PREAMBLE and before BEFORE_TABLES, so extension-provided types are available by the time tables are created. Both directions are idempotent and reversible.
Usage
from dbwarden import database_config
database_config(
database_name="primary",
database_type="postgresql",
database_url_sync="postgresql://...",
pg_extensions=["postgis", "hstore"],
)
Installation
dbwarden plugin add dbwarden-pgsql-extensions
Trust tier
This is an official dbwarden plugin. Its distribution name is classified before any of its code is imported, and dbwarden plugin add verifies the PyPI Trusted-Publishing attestation (PEP 740) against dbwarden-org/dbwarden-pgsql-extensions before installing. It loads automatically once installed, with no dbwarden plugin trust step.
Development
uv venv && uv pip install -e . -e ../dbwarden pytest
pytest -q
The tests/test_conformance.py suite runs dbwarden's shared conformance harness (dbwarden.plugin_conformance): entry point resolution, no import-time side effects, hook signatures, public-API-only imports, and idempotent setup().
License
MIT
Release files for dbwarden-pgsql-extensions 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dbwarden_pgsql_extensions-0.2.1.tar.gz | 13.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dbwarden_pgsql_extensions-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.6 kB
Release files / dbwarden_pgsql_extensions-0.2.1.tar.gz
| Download URL | dbwarden_pgsql_extensions-0.2.1.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1baba97c6788ede861f82f4e28d448669cdadf9522ff652da0a15448c0f2faa
|
|
BLAKE2b-256 checksum How to use checksums |
e7f3073823a0fca3ffad68be768f636111c078cfdb90c1eb3d440b00bdfb5a9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logRelease files / dbwarden_pgsql_extensions-0.2.1-py3-none-any.whl
| Download URL | dbwarden_pgsql_extensions-0.2.1-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b30d0924c638ab5724c17039b8fd126b42e469cb4b115a6f7874596ad62b3468
|
|
BLAKE2b-256 checksum How to use checksums |
140b5b6abafd775518e37c8e6f5ef11673816230501d3d731e4597302067fafa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency log