[PATCH] Updating documentation about bulding documentation in Windows.
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:t76134psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 27, 2026 at 09:19 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 t76134_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 t76134_1 && git checkout t76134_1Patchset v1 (message #1) is on t76134_1
Hello everyone.
Current documentation contains outdated instruction and scripts relative to
building documentation on Windows machine.
I removed useless scripts and wrote some guide to build docs using Windows
Linux Subsystem.
Also, could be viewed on github -
https://github.com/michail-nikolaev/postgres/commit/c6781351306810bfebab1fa5b454e8d24b9ea2f6
Thanks,
Michail.
On 1/23/18 16:05, Michail Nikolaev wrote:
Current documentation contains outdated instruction and scripts relative
to building documentation on Windows machine.I removed useless scripts and wrote some guide to build docs using
Windows Linux Subsystem.
Why not fix the script instead?
Using WSL is also a good idea, but then we could just say, use WSL and
follow the instructions for the particular Linux distribution. We don't
need to repeat all that again.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Hello.
It is not so easy to fix the script because it is based on old toolset
(probably on 9.6).
I'll try one more attempt.
Regardning WSL:
I think it is better to keep some instructions because there are a lot of
common errors - line ending, correct usage of linux\windows file system
mappings.
Most of Windows users are not familiar with it. I could rewrtite it as:
1. clone using WSL to Windows filesystem
2. disable autoclrf
3. edit documentation in Windows (usig Unix line-ending) and build in
WLS.
Thanks,
Michail.
пт, 26 янв. 2018 г. в 8:03, Peter Eisentraut <
peter.eisentraut@2ndquadrant.com>:
Show quoted text
On 1/23/18 16:05, Michail Nikolaev wrote:
Current documentation contains outdated instruction and scripts relative
to building documentation on Windows machine.I removed useless scripts and wrote some guide to build docs using
Windows Linux Subsystem.Why not fix the script instead?
Using WSL is also a good idea, but then we could just say, use WSL and
follow the instructions for the particular Linux distribution. We don't
need to repeat all that again.--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services