Update doc links to https where appropriate?
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:t38389psql -h localhost -U postgresBuilt from patchset v2 (message #2), July 27, 2026 at 08:56 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 t38389_2 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 t38389_2 && git checkout t38389_2Patchset v2 (message #2) is on t38389_2
Hi,
Writing up docs for JITing I noticed that nearlyall wikipedia links on
the acronyms page are http:// rather than https://. Seems like we should
update links in the docs when alternatives are available?
Any counterarguments?
Greetings,
Andres Freund
On 16 Mar 2018, at 19:54, Andres Freund <andres@anarazel.de> wrote:
Writing up docs for JITing I noticed that nearlyall wikipedia links on
the acronyms page are http:// rather than https://. Seems like we should
update links in the docs when alternatives are available?
I don’t see a reason why not, since we just incur a 307 redirect on all visits
otherwise. +1 for bumping them to https.
While in there, perhaps we should update our links to the expanded page on
Wikipedia to avoid an internal 304 redirect as well? The attached diff changes
the ones I found on a quick scan, but there might be others.
cheers ./daniel