Drop "leaked" resources in sqljson/sqljson_queryfuncs regression tests
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t253517psql -h localhost -U postgresBuilt from patchset v1 (message #1), August 23, 2026 at 11:09 PM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t253517_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t253517_1 && git checkout t253517_1Patchset v1 (message #1) is on t253517_1
Found these "leaks" while doing some other work in the SQL/JSON area.
Did some analysis to find that this should be backpatched through 17.
--
Tristan Partin
PostgreSQL Contributors Team
AWS (https://aws.amazon.com)
"Tristan Partin" <tristan@partin.io> writes:
Found these "leaks" while doing some other work in the SQL/JSON area.
Did some analysis to find that this should be backpatched through 17.
You sure those aren't intentional? One use of the regression
database's ending state is to serve as a test case for pg_upgrade,
so we like to leave around objects that are unique in some way.
regards, tom lane