Typo in libpq

Started by Daniel Gustafssonover 9 years ago2 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:t36374
psql -h localhost -U postgres

Built from patchset v1 (message #1), July 28, 2026 at 07:33 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 t36374_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 t36374_1 && git checkout t36374_1

Patchset v1 (message #1) is on t36374_1

Jump to latest
#1Daniel Gustafsson
daniel@yesql.se

There seems to be a typo in libpq as per attached, “..we will loose error
messages” should probably be “..we will lose error messages”.

cheers ./daniel

Attachments:

t36374_1
typo-libpq-loose.diffapplication/octet-stream; name=typo-libpq-loose.diffDownload+1-1
#2Magnus Hagander
magnus@hagander.net
In reply to: Daniel Gustafsson (#1)
Re: Typo in libpq

On Thu, Mar 30, 2017 at 3:48 PM, Daniel Gustafsson <daniel@yesql.se> wrote:

There seems to be a typo in libpq as per attached, “..we will loose error
messages” should probably be “..we will lose error messages”.

Applied, thanks.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/