Extra newlines added even if PQerrorMessage

Started by Michael Paquierover 8 years ago1 messageshackers
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:t38667
psql -h localhost -U postgres

Built from patchset v1 (message #1), July 27, 2026 at 08:31 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 t38667_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 t38667_1 && git checkout t38667_1

Patchset v1 (message #1) is on t38667_1

Jump to latest
#1Michael Paquier
michael@paquier.xyz

Hi all,

2f52518 has removed a couple of extra newlines not needed as
PQerrorMessage is used, but some places have been missed:
- testlo64.c
- testlo.c
- findoidjoins.c
Those are not really critical, still I think that it would be good
practice to be consistent.

pgbench uses at one place CommandFailed() which appends automatically a
newline for the message passed by the caller, and calls one
PQerrorMessage. Perhaps CommandFailed()'s callers should just define a
newline in the message? Or it could be better to have a version of
pchomp for frontends?

Thanks,
--
Michael

Attachments:

t38667_1
pqerror-newlines.patchtext/x-diff; charset=us-asciiDownload+12-12