On Wed, May 2, 2018 at 1:27 AM, Stas Kelvich <s.kelvich@postgrespro.ru> wrote:
> 1) To achieve commit atomicity of different nodes intermediate step is
> introduced: at first running transaction is marked as InDoubt on all nodes,
> and only after that each node commit it and stamps with a given GlobalCSN.
> All readers who ran into tuples of an InDoubt transaction should wait until
> it ends and recheck visibility.
I'm concerned that long-running transaction could keep other
transactions waiting and then the system gets stuck. Can this happen?
and is there any workaround?
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
