Avoid resource leak (src/bin/pg_resetwal/pg_resetwal.c)
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:t52526psql -h localhost -U postgresBuilt from patchset v1 (message #1), September 20, 2026 at 09:29 AM.
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 t52526_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 t52526_1 && git checkout t52526_1Patchset v1 (message #1) is on t52526_1
Hi.
Per Coverity.
The function *read_controlfile* is responsible for updating old pg_control
versions.
Coverity complains that the struct ControlFileData buffer is leaked.
I think that is right.
Trivial patch attached.
best regards,
Ranier Vilela
On Thu, Oct 23, 2025 at 09:26:24PM -0300, Ranier Vilela wrote:
The function *read_controlfile* is responsible for updating old pg_control
versions.
Coverity complains that the struct ControlFileData buffer is leaked.I think that is right.
Bis repetita. Allocation in the context of a short-term binary
execution.
--
Michael