• Heikki Linnakangas's avatar
    Correctly detect SSI conflicts of prepared transactions after crash. · d6a72719
    Heikki Linnakangas authored
    A prepared transaction can get new conflicts in and out after preparing, so
    we cannot rely on the in- and out-flags stored in the statefile at prepare-
    time. As a quick fix, make the conservative assumption that after a restart,
    all prepared transactions are considered to have both in- and out-conflicts.
    That can lead to unnecessary rollbacks after a crash, but that shouldn't be
    a big problem in practice; you don't want prepared transactions to hang
    around for a long time anyway.
    
    Dan Ports
    d6a72719
predicate.c 155 KB