Small typo in func.sgml
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:t76593psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 03: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 t76593_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 t76593_1 && git checkout t76593_1Patchset v1 (message #1) is on t76593_1
I thinkk a new line is needed after <para>.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
On Thu, Nov 07, 2019 at 08:16:15AM +0900, Tatsuo Ishii wrote:
I think a new line is needed after <para>.
True that it is the usual pattern.
--
Michael
Tatsuo Ishii <ishii@sraoss.co.jp> writes:
I thinkk a new line is needed after <para>.
- <para>JSON query functions and operators + <para> + JSON query functions and operators
It doesn't really make any difference, I believe. I agree it's
neater with the newline, but I wouldn't bother changing it unless
you're making some other nearby change.
(There are actually instances of this in quite a few places in
our docs, if memory serves. I think somebody uses, or used,
an editor that tended to remove newlines in that context.)
regards, tom lane