Hello, I have a question that involves two Aurora Postgres RDS clusters.
I have two clusters. With long-running transactions, one of them is able to create a replication slot when a record is inserted into a table while the other does not and is blocked. It does create the replication slot when the transaction is committed. I wanted to know if this behavior is actually an anomaly or there is a misconfiguration with the parameters that is creating the replication slot when it should be blocked? Also, for the long running transactions, the transaction isolation level is *read committed *for both the clusters. Thank you, Amritanshu
