Bogus tab completion tweak for UPDATE ... SET ... =
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:t36240psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 07:56 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 t36240_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 t36240_1 && git checkout t36240_1Patchset v1 (message #1) is on t36240_1
Hi,
Even though the following is coincidentally meaningful, I don't think
it was intentional or is useful:
postgres=# update foo set x = DEFAULT
Shouldn't that completion should be suppressed, like in the attached?
--
Thomas Munro
http://www.enterprisedb.com
Thomas Munro <thomas.munro@enterprisedb.com> writes:
Even though the following is coincidentally meaningful, I don't think
it was intentional or is useful:
postgres=# update foo set x = DEFAULT
Uh, seems perfectly sane to me. Why should we assume that can't be
what the user wants?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers