WRT the "tag A insert on conflict do nothing & read again" topic: as far as I understand, this should only be an issue with isolation level repeatable-read and serialisable. In read committed it shouldn't be an issue since transaction 2 will only resume and attempt the interest (and get the conflict error) only after transaction 1 commits and releases the row lock. As a result, the subsequent read on repeatable that transaction 2 shroud be able to find tag A. Am I missing something?
WRT the "tag A insert on conflict do nothing & read again" topic: as far as I understand, this should only be an issue with isolation level repeatable-read and serialisable. In read committed it shouldn't be an issue since transaction 2 will only resume and attempt the interest (and get the conflict error) only after transaction 1 commits and releases the row lock. As a result, the subsequent read on repeatable that transaction 2 shroud be able to find tag A. Am I missing something?
woaaaa freddy mercury came to the podcast!!!!!