Errors in documentation

Started by Alexander Lakhinabout 9 years ago2 messagesdocs
Beta feature

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.

won't retrysuccessCI history

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:t76004
psql -h localhost -U postgres

Built from patchset v1 (message #1), July 28, 2026 at 05:30 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 t76004_1 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t76004_1 && git checkout t76004_1

Patchset v1 (message #1) is on t76004_1

Jump to latest
#1Alexander Lakhin
exclusion@gmail.com

Hello,

Please consider committing attached patches to the documentation.
A pair of the patches I sent before (see
/messages/by-id/374e84e6-f89b-4d0a-652c-cb2449f0bfc4@gmail.com),
but they weren't committed.
If some of these patches are not valid or raise any questions, please
let me know.

Best

--
Alexander Lakhin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Attachments:

t76004_1
alter_table-tags-comma.patchtext/x-patch; name=alter_table-tags-comma.patchDownload+2-2
are-are.patchtext/x-patch; name=are-are.patchDownload+2-2
catalogs-Name_name.patchtext/x-patch; name=catalogs-Name_name.patchDownload+1-1
copy-input_insert.patchtext/x-patch; name=copy-input_insert.patchDownload+1-1
create_table-fix-a-sentence.patchtext/x-patch; name=create_table-fix-a-sentence.patchDownload+2-2
event-trigger-table.patchtext/x-patch; name=event-trigger-table.patchDownload+1-0
failback.patchtext/x-patch; name=failback.patchDownload+1-1
indexam-structname.patchtext/x-patch; name=indexam-structname.patchDownload+1-1
logicaldecoding-pg_stat_replication-link.patchtext/x-patch; name=logicaldecoding-pg_stat_replication-link.patchDownload+1-1
perform-space.patchtext/x-patch; name=perform-space.patchDownload+1-1
readded.patchtext/x-patch; name=readded.patchDownload+2-2
release-10-misplaced-comma.patchtext/x-patch; name=release-10-misplaced-comma.patchDownload+1-1
release-10-one-man.patchtext/x-patch; name=release-10-one-man.patchDownload+1-1
updateable.patchtext/x-patch; name=updateable.patchDownload+3-3
#2Peter Eisentraut
peter_e@gmx.net
In reply to: Alexander Lakhin (#1)
Re: Errors in documentation

On 8/23/17 10:42, Alexander Lakhin wrote:

Please consider committing attached patches to the documentation.
A pair of the patches I sent before (see
/messages/by-id/374e84e6-f89b-4d0a-652c-cb2449f0bfc4@gmail.com),
but they weren't committed.
If some of these patches are not valid or raise any questions, please
let me know.

I have committed these patches, except the "readded" and "failback"
patches, which were incorrect, and the changes to very old release
notes, which we typically don't change.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs