Repository navigation
v1.16.0 — PostgreSQL 19 support
Warning: the pg_mentat tarballs in this release need glibc 2.38+ and do not load on Debian 12, Ubuntu 22.04, RHEL 9 or Amazon Linux 2023 (#336). Use v1.16.1, which also fixes get-else in multi-pattern queries.
mentat 1.16.0: PostgreSQL 19 support
pg_mentat now builds and runs on PostgreSQL 19, tested on 19rc1. Until
now pg_mentat could not be built on PostgreSQL 19: the pgrx 0.17 it was built
with has no PostgreSQL 19 bindings.
1.16.0 moves to pgrx 0.19.3, which supports PostgreSQL 13–19. pg_mentat needed
no code changes. The full test suite (1934 tests with scripting) passes on
PostgreSQL 13, 14, 15, 16, 17, 18 and 19rc1.
New
- Release tarballs for PostgreSQL 18 and 19. The assets now include
pg_mentat-pg15…pg_mentat-pg19. The PG19 build uses PGDG's
postgresql-19(19~rc1) package. - CI tests PostgreSQL 13–19.
Changed
-
Building from source needs Rust 1.96 and
cargo-pgrx0.19.3:cargo install --locked cargo-pgrx --version 0.19.3 cargo pgrx init --pg19 $(which pg_config) cargo pgrx install --release --no-default-features --features pg19The library crates on crates.io (
mentatdband friends) still build on
Rust 1.88. -
duckdb 1.10506.1. This moves its build-time
zipdependency to 9.x, which
fixes RUSTSEC-2026-0367/0368/0369.
Upgrading
- PostgreSQL:
ALTER EXTENSION pg_mentat UPDATE TO '1.16.0';. This is a
no-op step with no schema change. Reinstall the.sofor your PostgreSQL
major first. - Nix:
pg_mentat-pg14…pg_mentat-pg18are unchanged. There is no
pg_mentat-pg19yet, because nixpkgs doesn't have a PostgreSQL 19 release
build.
Known issue
A non-superuser still can't CREATE EXTENSION pg_mentat. It fails with
permission denied for language c. This is
#331, reopened. The 1.13.0
"trusted install" change never worked, and 1.15.0 fails the same way. Install
as a superuser for now. The fix changes who can access the mentat schema, so
it will get its own release.
Full details: CHANGELOG.