I was hoping you could give me some insights about how this bug might appear with multiple replications slots. For example if I have two replication slots would you expect both slots to see the same error, even if they were started, consumed or the LSN was confirmed-flushed at different times?
from my mail above -- as we see, this issue creates problems in the field. Moreover, the patch is trivial and hopefully I've shown that ERROR triggers were spurious and there is no easy way to relax the check.
