Fix comment in pg_upgrade
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:t37764psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 26, 2026 at 04:43 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 t37764_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 t37764_1 && git checkout t37764_1Patchset v1 (message #1) is on t37764_1
On Wed, Nov 22, 2017 at 2:45 PM, Daniel Gustafsson <daniel@yesql.se> wrote:
Attached patch removes a stray word in a comment in
pg_upgrade/relfilenode.c
which got left behind back in commit 29add0de4920e4f448a30bfc35798b
939c211d97.
Applied, thanks.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>