Missing whitespace in pg_dump docs
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:t76338psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 01: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 t76338_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 t76338_1 && git checkout t76338_1Patchset v1 (message #1) is on t76338_1
On Fri, Oct 26, 2018 at 3:27 PM Daniel Gustafsson <daniel@yesql.se> wrote:
The attached diff adds what seems to be a missing whitespace in the
discussion
on dump formats.
Pushed, thanks.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>