Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object

Hi,

I tested the latest v8-0001 patch on current master and wanted to share my
observations.

Before applying the patch, when dropping a column, constraints and indexes
that referenced the whole row (for example, CHECK (ts = ROW(...)) or
expressions using ts) were not removed. This left the table in an
inconsistent state and resulted in errors during inserts.

After applying the patch, these objects are correctly detected and removed
when the column is dropped. The table remains clean, and inserts work as
expected.

I also tried a few additional scenarios:

-

DROP COLUMN with CASCADE—behaved as expected, no leftover objects
-

normal column-level constraints — still handled correctly (no regression)
-

multiple whole-row constraints — all removed properly
-

ALTER COLUMN TYPE — correctly throws an error when a whole-row
constraint exists

Overall, the behavior looks correct and consistent based on these tests.

Thanks for working on this!
lakshmi