mirror of https://referencesource.org/postgres-extension-postgresql-version-compatibility/
2da0ce2 verified | pretty_name: "PostgreSQL extension compatibility with PostgreSQL major versions" | |
| license: other | |
| license_name: source-terms-cited | |
| license_link: https://referencesource.org/postgres-extension-postgresql-version-compatibility/ | |
| language: | |
| - en | |
| tags: | |
| - reference-data | |
| - provenance | |
| - referencesource-org | |
| configs: | |
| - config_name: default | |
| data_files: | |
| - split: train | |
| path: data/records.jsonl | |
| # PostgreSQL extension compatibility with PostgreSQL major versions | |
| **Canonical, always-current version: https://referencesource.org/postgres-extension-postgresql-version-compatibility/** | |
| Machine-readable: https://referencesource.org/postgres-extension-postgresql-version-compatibility/data.json — this mirror is a point-in-time copy. | |
| - **Last verified:** 2026-09-28 | |
| - **Stale after:** 2027-01-26 (past this date, prefer the canonical copy — | |
| it re-verifies on a cadence this snapshot does not) | |
| - **Records:** 9 | |
| Which major versions of PostgreSQL a popular server extension supports, taken from that extension's own documentation, README or changelog -- not from any one cloud vendor's managed-service certification list. Before upgrading a self-hosted PostgreSQL server, an operator running several extensions has to check every extension's supported range separately, because dropping support for an old PostgreSQL version and adding support for a new one happen on each extension's own schedule, not in step with Postgres itself or with each other. Cloud vendors (Azure, AWS/Aurora, DigitalOcean, Alibaba) each publish their own extension-by-version table, but that shows what the vendor has certified for its managed service, which lags or diverges from what the extension's own maintainers say it supports; no vendor-neutral page was found that cites each extension's own documentation. Some projects state a range in one sentence; others state only that a particular release added or dropped a PostgreSQL version, and the range has to be read off those entries. Both are recorded here, and which one a record rests on is visible from its quote. | |
| ## Provenance — what every record carries | |
| Every record carries `source` (the URL the value was read from) and | |
| `source_quote` (a verbatim quote from that page stating it). A value you | |
| cannot check against its page is indistinguishable from an invented one; | |
| these can all be checked. Each record is also individually addressable on | |
| the canonical site at its `url`. | |
| ## Licence position | |
| unknown | |
| Facts are not copyrightable; what this dataset takes from each source is a | |
| fact plus a short attributed quote linking back to the page that states it. | |
| ## Sources | |
| - https://raw.githubusercontent.com/citusdata/citus/main/CHANGELOG.md | |
| - https://raw.githubusercontent.com/HypoPG/hypopg/master/README.md | |
| - https://raw.githubusercontent.com/citusdata/pg_cron/main/README.md | |
| - https://raw.githubusercontent.com/pgpartman/pg_partman/master/README.md | |
| - https://raw.githubusercontent.com/pgaudit/pgaudit/master/README.md | |
| - https://github.com/pgvector/pgvector | |
| - https://www.postgis.net/docs/manual-3.5/postgis_installation.html | |
| - https://docs.timescale.com/self-hosted/latest/upgrades/upgrade-pg/ | |
| - https://raw.githubusercontent.com/eulerto/wal2json/master/README.md | |
| ## Fields | |
| See any record in `data/records.jsonl` — field names are self-describing, | |
| and the canonical page for each record renders them with labels: | |
| https://referencesource.org/postgres-extension-postgresql-version-compatibility/ | |