CREATE TABLE t (a INT PRIMARY KEY, b BOOLEAN DEFAULT FALSE);
CREATE VIEW v AS SELECT a from t;
ALTER TABLE t DROP COLUMN b;

says

pq: cannot drop column "b" because view "v" depends on it

This is a result of #17280 because our previous attempt at being fine-grained was erroneous. However the result errs on the other side of the UX inconvenience.

There should be a middle ground that looks just as those columns actually mentioned in the view query.