Remove extra spaces
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:t45321psql -h localhost -U postgresBuilt from patchset v1 (message #1), September 20, 2026 at 11:37 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 t45321_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 t45321_1 && git checkout t45321_1Patchset v1 (message #1) is on t45321_1
Hi,
While browsing the code, noticed the extra spaces after the function name.
Removed the same in the attached patch.
--
--
Thanks & Regards,
Suraj kharage,
edbpostgres.com
Suraj Kharage <suraj.kharage@enterprisedb.com> writes:
While browsing the code, noticed the extra spaces after the function name.
Removed the same in the attached patch.
I'm afraid that's a waste of time because the next pgindent run
will just put them back. "numeric" is also a typedef name and
this usage of it seems to confuse pgindent. If you wanted to
dive into the pgindent code and fix that bug in it, that'd be
great, but the return-on-effort is probably going to be poor.
(Another possibility is to change the C function name.)
regards, tom lane