0

I'm worried that unfortunately there's not a great way to handle this.

Here's what happened:

  1. Schema change made in main database
  2. Logically replicated db has issue with subscription given the identity change
  3. Subscription failed
  4. Inactive replication slot in pg_replication_slots

Is there anyway to get back and not lose any of the data that the WAL has written? For example, I've tried the following on the replication server:

ALTER SUBSCRIPTION "my_subscription" REFRESH PUBLICATION;
ALTER SUBSCRIPTION "my_subscription" ENABLE;

but it still doesn't work. Any thoughts?

jlarks32
  • 931
  • 8
  • 20
  • Presumably you just have to fix the problem. You didn't tell us what the problem is, other than "the identity change", so we can advise you on how to fix it. – jjanes Nov 15 '22 at 15:53

0 Answers0