Trailing semicolons on partitioning example commands
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:t76136psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 27, 2026 at 09:15 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 t76136_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 t76136_1 && git checkout t76136_1Patchset v1 (message #1) is on t76136_1
Is there a reason for not ending all partitioning commands with semicolons in
the declarative partitioning example?
https://www.postgresql.org/docs/devel/static/ddl-partitioning.html
The two last commands with TABLESPACE clauses are ended with semicolons, the
first three arent. Attached patch adds semicolons such that all are properly
ended.
cheers ./daniel
On Fri, Jan 26, 2018 at 3:27 PM, Daniel Gustafsson <daniel@yesql.se> wrote:
Is there a reason for not ending all partitioning commands with semicolons
in
the declarative partitioning example?https://www.postgresql.org/docs/devel/static/ddl-partitioning.html
The two last commands with TABLESPACE clauses are ended with semicolons,
the
first three arent. Attached patch adds semicolons such that all are
properly
ended.
I cant see one, since all the other examples do.
Thus, pushed. Thanks!
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>