Workers: Having a problem when syncing schema SequelizeDatabaseError: tuple concurrently updated

[jiqiang90]

Prerequisites

• Are you running the latest version(s)?
• Did you check the debugging guide?
• Did you check the FAQs and Discussions?
• Are you reporting to the correct repository?
• Did you search for an existing issue or pull request?

Description

with latest dev version 1.16.1-2

running any project with workers will throw this error

2022-12-11T21:00:26.350Z <store> ERROR Having a problem when syncing schema SequelizeDatabaseError: tuple concurrently updated

I suspect this is casing by trigger been concurrently created

2022-12-11T21:02:13.464Z <db> DEBUG Executing (default): CREATE OR REPLACE FUNCTION "0x438aafbff88b36a0"()
    RETURNS trigger AS $$
  BEGIN
    PERFORM pg_notify(
            '0xa44d38839d65227b',
            'schema_updated');
    RETURN NULL;
  END;
  $$ LANGUAGE plpgsql; 
2022-12-11T21:02:13.465Z <db> DEBUG Executing (default): CREATE OR REPLACE FUNCTION "0x438aafbff88b36a0"()
    RETURNS trigger AS $$
  BEGIN
    PERFORM pg_notify(
            '0xa44d38839d65227b',
            'schema_updated');
    RETURN NULL;
  END;
  $$ LANGUAGE plpgsql; 

Details

These details can help to reproduce the environment the issue is occurring

Local Environment: [You can get this information from executing subql version.]
Query Version: [What is the version of the query service?]
Indexer Version: [What is the version of the indexer service?]
Network Details:

• [Network]
• [Block height, a block height where the issue is happening]
• [Dictionary endpoint, if used]

Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

Example project: [A link to a minimal example that can reproduce the issue]

Expected behavior: [What you expected to happen]

Actual behavior: [What actually happened]

Any other information

Is there any other information you would like to add?