You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Change many routines to return ObjectAddress rather than OID
The changed routines are mostly those that can be directly called byProcessUtilitySlow; the intention is to make the affected objectinformation more precise, in support for future event trigger changes.Originally it was envisioned that the OID of the affected object wouldbe enough, and in most cases that is correct, but upon actuallyimplementing the event trigger changes it turned out that ObjectAddressis more widely useful.Additionally, some command execution routines grew an output argumentthat's an object address which provides further info about the executedcommand. To wit:* for ALTER DOMAIN / ADD CONSTRAINT, it corresponds to the address of the new constraint* for ALTER OBJECT / SET SCHEMA, it corresponds to the address of the schema that originally contained the object.* for ALTER EXTENSION {ADD, DROP} OBJECT, it corresponds to the address of the object added to or dropped from the extension.There's no user-visible change in this commit, and no functional changeeither.Discussion: 20150218213255.GC6717@tamriel.snowman.netReviewed-By: Stephen Frost, Andres Freund