Hi list The attached patch changes the behavior of multiple ALTER x SET SCHEMA commands, to skip, rather than fail, when the old and new schema is the same.
The advantage is that it's now easier to write DDL scripts that are indempotent. This already matches the behavior of ALTER EXTENSION SET SCHEMA in earlier versions, as well as many other SET-ish commands, e.g. ALTER TABLE SET TABLESPACE, OWNER TO, CLUSTER ON, SET (storage_parameter...) etc. I don't see why SET SCHEMA should be treated any differently. The code is written such that object_access_hook is still called for each object. Regression tests included. I couldn't find any documentation that needs changing. Regards, Marti
0001-Skip-ALTER-x-SET-SCHEMA-if-the-schema-didn-t-change.patch
Description: binary/octet-stream
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
