My last deployment failed on my prod DB. I used hasura's built-in `updated_at` helper and I encountered this error:
```
{"level":"error","msg":"skipping applying migrations on database , encountered:
{
"code": "postgres-error",
"error": "query execution failed",
"internal": {
"arguments": [],
"error": {
"description": null,
"exec_status": "FatalError",
"hint": null,
"message": "must be owner of function set_current_timestamp_updated_at",
"status_code": "42501"
},
"prepared": false,
"statement": "CREATE TABLE "public"."slacks" ("id" uuid NOT NULL DEFAULT gen_random_uuid(), "created_at" timestamptz NOT NULL DEFAULT now(), "updated_at" timestamptz NOT NULL DEFAULT now(), "group_id" uuid NOT NULL, "url" text NOT NULL, "name" text NOT NULL, PRIMARY KEY ("id") , FOREIGN KEY ("group_id") REFERENCES "public"."groups"("id") ON UPDATE cascade ON DELETE cascade);COMMENT ON TABLE "public"."slacks" IS E'Slack webhooks';\
CREATE OR REPLACE FUNCTION "public"."set_current_timestamp_updated_at"()\
RETURNS TRIGGER AS $$\
DECLARE\
_new record;\
BEGIN\
_new := NEW;\
_new."updated_at" = NOW();\
RETURN _new;\
END;\
$$ LANGUAGE plpgsql;\
CREATE TRIGGER "set_public_slacks_updated_at"\
BEFORE UPDATE ON "public"."slacks"\
FOR EACH ROW\
EXECUTE PROCEDURE "public"."set_current_timestamp_updated_at"();\
COMMENT ON TRIGGER "set_public_slacks_updated_at" ON "public"."slacks" \
IS 'trigger to set value of column "updated_at" to current timestamp on row update';\
CREATE EXTENSION IF NOT EXISTS pgcrypto;\
"
},
"path": "$"
}","time":"2022-11-11T09:56:22Z"}
```
