aboutsummaryrefslogtreecommitdiff
path: root/src/test/modules/commit_ts/expected/git@kaiwu.me:public/postgresql
diff options
context:
space:
mode:
authorÁlvaro Herrera <alvherre@kurilemu.de>2025-07-04 18:05:43 +0200
committerÁlvaro Herrera <alvherre@kurilemu.de>2025-07-04 18:05:43 +0200
commitf295494d338c452617f966d4d1f13a726cd72661 (patch)
tree907b749805ff96868a5a09f462d94e0997dae4f6 /src/test/modules/commit_ts/expected/git@kaiwu.me:public/postgresql
parentd64d68fddf9802dea4cc5be8a491937c3aefefa0 (diff)
downloadpostgresql-f295494d338c452617f966d4d1f13a726cd72661.tar.gz
postgresql-f295494d338c452617f966d4d1f13a726cd72661.zip
pg_upgrade: check for inconsistencies in not-null constraints w/inheritance
With tables defined like this, CREATE TABLE ip (id int PRIMARY KEY); CREATE TABLE ic (id int) INHERITS (ip); ALTER TABLE ic ALTER id DROP NOT NULL; pg_upgrade fails during the schema restore phase due to this error: ERROR: column "id" in child table must be marked NOT NULL This can only be fixed by marking the child column as NOT NULL before the upgrade, which could take an arbitrary amount of time (because ic's data must be scanned). Have pg_upgrade's check mode warn if that condition is found, so that users know what to adjust before running the upgrade for real. Author: Ali Akbar <the.apaan@gmail.com> Reviewed-by: Justin Pryzby <pryzby@telsasoft.com> Backpatch-through: 13 Discussion: https://postgr.es/m/CACQjQLoMsE+1pyLe98pi0KvPG2jQQ94LWJ+PTiLgVRK4B=i_jg@mail.gmail.com
Diffstat (limited to 'src/test/modules/commit_ts/expected/git@kaiwu.me:public/postgresql')
0 files changed, 0 insertions, 0 deletions