hasura / hasura/graphql-engine

function hdb_catalog.notify_hasura_comments_UPDATE() does not exist

Open
#9,270 2 comments 0 reactions 0 assignees View on GitHub
k/bug
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### VERSIONS:

postgres:
image: postgres:12
graphql-engine:
image: hasura/graphql-engine:v2.10.1

### ERROR:
WARN Metadata is inconsistent
WARN Use 'hasura metadata ic list' command to list inconsistent objects
ERRO skipping applying migrations on database gunza, encountered:
{
"code": "postgres-error",
"error": "query execution failed",
"internal": {
"arguments": [],
"error": {
"description": null,
"exec_status": "FatalError",
"hint": null,
"message": "function hdb_catalog.notify_hasura_comments_UPDATE() does not exist",
"status_code": "42883"
},
"prepared": false,

Error occures when i trying to deploy my metadata/migrations to new clear hasura with same version. On the current hasura migrations are set properly

![image](https://user-images.githubusercontent.com/66596500/205891889-04882f19-4f65-4757-81c8-1505a67d70da.png)

Contributor guide

Open the contributing guide

Research direction

Start by running `hasura metadata ic list` and inspect the metadata/migrations deployment against the PostgreSQL 12 database. Trace where the missing `hdb_catalog.notify_hasura_comments_UPDATE()` function is expected, then confirm that deploying the reported metadata and migrations to a clean Hasura v2.10.1 instance completes without the PostgreSQL error.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.