| From: | lakshmi <lakshmigcdac(at)gmail(dot)com> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, 金 <jinbinge(at)126(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Subject: | Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object |
| Date: | 2026-07-20 05:52:52 |
| Message-ID: | CAEvyyTipCQ+EXugcVL0wkm7xenX_xeRneDf510dHAG6HAWgC_g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Jian,
I tested the latest v14 patch on current master.Everything worked as
expected in my testing. I verified that whole-row referenced constraints
and indexes are handled correctly when dropping a column, and that ALTER
COLUMN SET DATA TYPE still reports an error when whole-row dependent
objects exist. I also tested the newly merged trigger and row-level
security policy cases. ALTER TABLE ... DROP COLUMN correctly reports
dependency errors when a whole-row reference exists, and using CASCADE
removes the dependent trigger or policy as expected. I also verified that
the remaining table definition is correct after the operation, and I didn't
notice any unexpected behavior during testing.
Thanks for the update.
regards
lakshmi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wenhui qiu | 2026-07-20 06:23:59 | Re: WAL compression setting after PostgreSQL LZ4 default change |
| Previous Message | Hayato Kuroda (Fujitsu) | 2026-07-20 05:50:51 | RE: sequencesync worker race with REFRESH SEQUENCES |