Another point for backpatch: EnableDisableTrigger() changes API, which is potentially not good. In backbranches I'll keep the function unchanged and add another function with the added argument, EnableDisableTriggerNew().
So extensions that want to be compatible with both old and current versions (assuming any users of that function exist out of core; I didn't find any) could do something like #if PG_VERSION_NUM <= 160000 EnableDisableTriggerNew( all args ) #else EnableDisableTrigger( all args ) #endif and otherwise they're compatible as compiled today. Since there are no known users of this interface, it doesn't seem to warrant any more convenient treatment. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "Those who use electric razors are infidels destined to burn in hell while we drink from rivers of beer, download free vids and mingle with naked well shaved babes." (http://slashdot.org/comments.pl?sid=44793&cid=4647152)