Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object - Mailing list pgsql-hackers

From lakshmi
Subject Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object
Date
Msg-id CAEvyyTipCQ+EXugcVL0wkm7xenX_xeRneDf510dHAG6HAWgC_g@mail.gmail.com
Whole thread
In response to Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object  (jian he <jian.universality@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: sequencesync worker race with REFRESH SEQUENCES
Next
From: wenhui qiu
Date:
Subject: Re: WAL compression setting after PostgreSQL LZ4 default change