> I've attached the latest version patches. I've incorporated the review
> comments I got so far and improved locking strategy.
I want to ask a question about streaming replication with 2PC.
Are you going to support 2PC with streaming replication?
I tried streaming replication using v23 patches.
I confirm that 2PC works with streaming replication,
which there are primary/standby coordinator.
But, in my understanding, the WAL of "PREPARE" and
"COMMIT/ABORT PREPARED" can't be replicated to the standby server in
sync.
If this is right, the unresolved transaction can be occurred.
For example,
1. PREPARE is done
2. crash primary before the WAL related to PREPARE is
replicated to the standby server
3. promote standby server // but can't execute "ABORT PREPARED"
In above case, the remote server has the unresolved transaction.
Can we solve this problem to support in-sync replication?
But, I think some users use async replication for performance.
Do we need to document the limitation or make another solution?
Regards,
--
Masahiro Ikeda
NTT DATA CORPORATION