pg_language(langispl) column apparently not needed

Started by Antonin Houskaover 2 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.

appliestests failedCI 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:t49141
psql -h localhost -U postgres

Built from patchset v1 (message #1), October 22, 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 t49141_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 t49141_1 && git checkout t49141_1

Patchset v1 (message #1) is on t49141_1

Jump to latest
#1Antonin Houska
ah@cybertec.at

I couldn't find a reference to the 'langispl' attribute, so I removed it (see
the diff attached) and the master branch compiled cleanly. Is there yet a
reason to keep it?

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

Attachments:

t49141_1
remove_lanispl.difftext/x-diffDownload+0-4
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Antonin Houska (#1)
Re: pg_language(langispl) column apparently not needed

Antonin Houska <ah@cybertec.at> writes:

I couldn't find a reference to the 'langispl' attribute, so I removed it (see
the diff attached) and the master branch compiled cleanly. Is there yet a
reason to keep it?

You didn't test pg_dump, I take it.

regards, tom lane