Environment

Cloud

What is the current behaviour?

If you connect a Postgres database that runs in Heroku to your Hasura instance, you cannot create Event Triggers on Hasura.

The reason is that Heroku doesn't allow creating Postgres extensions in the public schema. Heroku only allow creating extensions in a schema called heroku_ext.

What is the expected behaviour?

Be able to create event triggers on Postgres databases that run in Heroku.

How to reproduce the issue?

1. Create a new Hasura cloud instance and connect a Postgres DB that runs in Heroku.
2. Go to the page to create an event trigger: https://cloud.hasura.io/project/<PROJECT_ID>/console/events/data/add
3. Try to create an event trigger.

Screenshots or Screencast

Please provide any traces or logs that could help here.

{
    "statement": "CREATE EXTENSION IF NOT EXISTS pgcrypto SCHEMA public",
    "prepared": false,
    "error": {
        "exec_status": "FatalError",
        "hint": null,
        "message": "Extensions can only be created on heroku_ext schema",
        "status_code": "P0001",
        "description": null
    },
    "arguments": []
}

Any possible solutions?

Maybe during the event trigger creation, having a field that allows defining in which schema the extensions should be created.

Can you identify the location in the source code where the problem exists?

No.

If the bug is confirmed, would you be willing to submit a PR?

No.

Keywords

event, triggers, heroku, postgres, error, heroku_ext, schema, public