Currently, the event triggers are recreated every time the metadata is reloaded, this behaviour is a bug. In v1.3.3, the event triggers were re-created only when:

1. The definition of the event trigger has changed in the metadata
2. The table's structure has altered (example: an old column has been dropped from the table)

In v2, in the reload_metadata API we can accept a new key called recreate_event_triggers which will either accept a boolean value or a list of source names like what we have for reload_sources. When the value of the key is an array, then we'll recreate the event triggers for only those sources.

The body of the request will look like:

{
    "type" : "reload_metadata",
    "args": {
        "reload_remote_schemas": true,
        "reload_sources": false,
        "recreate_event_triggers": ["source1", "source2"]
    }
}

From Tiru:

The reason why someone will want to recreate_event_triggers is if they removed the Postgres triggers manually for any reason.