Remove 'IN' from pg_freespace docs for consistency

Started by Bharath Rupireddyover 4 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.

appliessuccessCI 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:t45487
psql -h localhost -U postgres

Built from patchset v1 (message #1), October 06, 2026 at 11:54 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 t45487_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 t45487_1 && git checkout t45487_1

Patchset v1 (message #1) is on t45487_1

Jump to latest
#1Bharath Rupireddy
bharath.rupireddyforpostgres@gmail.com

Hi,

It seems like 'IN' isn't used for description of a function input
parameter in the docs unlike 'OUT'. AFAICS this is consistent across
the docs except the function pg_freespace. Attaching a tiny patch to
remove 'IN' there.

Thoughts?

Regards,
Bharath Rupireddy.

Attachments:

t45487_1
v1-0001-Remove-IN-from-pg_freespace-docs-for-consistency.patchapplication/octet-stream; name=v1-0001-Remove-IN-from-pg_freespace-docs-for-consistency.patchDownload+2-3