Note that ALTER TABLE cannot alter generated stored columns
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:t77005psql -h localhost -U postgresBuilt from patchset v1 (message #1), September 20, 2026 at 07:58 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 t77005_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 t77005_1 && git checkout t77005_1Patchset v1 (message #1) is on t77005_1
I was trying to change the generation expression of a generated stored
column using ALTER TABLE. It took me a while before I figured SET
GENERATED applies only to generated identity columns. I think it'd be
useful to note this in the documentation with something like the
attached.
On Sun, 2021-05-30 at 16:25 +0300, Emre Hasegeli wrote:
I was trying to change the generation expression of a generated stored
column using ALTER TABLE. It took me a while before I figured SET
GENERATED applies only to generated identity columns. I think it'd be
useful to note this in the documentation with something like the
attached.
+1
Yours,
Laurenz Albe
On 30.05.21 15:25, Emre Hasegeli wrote:
I was trying to change the generation expression of a generated stored
column using ALTER TABLE. It took me a while before I figured SET
GENERATED applies only to generated identity columns. I think it'd be
useful to note this in the documentation with something like the
attached.
I don't follow why you put this documentation under ALTER TABLE ... DROP
EXPRESSION. That action doesn't seem related to what you were hoping to do.
I don't follow why you put this documentation under ALTER TABLE ... DROP
EXPRESSION. That action doesn't seem related to what you were hoping to do.
I thought that's where it would be if we had ADD/SET EXPRESSION
statements, just like the ADD/SET GENERATED statements just below.