Skip to content

Issues that came up when implementing #1

@michaelwills

Description

@michaelwills

Thank you for this! I have two replicas in other regions running 🚀!

I hit a few issues which I may be able to make a PR for in the coming days. They aren't major but did take a bit of digging:

Briefly:

  • Being new to replication, I didn't realize each subscription needs a unique name
  • I had the pg_graphql extension enabled on my primary. Executing the schema on the read replicas didn't fail, but the resultant structure didn't actually match. graph._type was the first error. I disabled graphql which brought that part in line.
  • New projects have pgsodium enabled by default it seams, making the schema's different. My primary was from several months back.
  • Enabling pgsodium on the primary does add it to the schema dump, but it fails as the pgsodium.key relation wasn't found. I'll have to check my notes for the error.
  • Disabling pgsodium manually on all three, going through the steps, then re-enabling them afterwards worked. Doing a structure diff showed they were all identical. Extensions were all a go then.
  • Data still didn't update so I put in all the log levels just in case. The logging Errors template doesn't include Warning which is needed to see the worker error.

Once I updated the max workers and restarted it immediately backfilled and changes were being propagated.

Thanks again!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions