= Database transaction
A <database transaction> groups <database> operations into a unit that can be committed or rolled back. <Transaction atomicity> means that its updates take effect together or not at all. <Transaction durability> concerns retaining an acknowledged committed result after a failure; <transaction isolation> controls which effects concurrent <database transactions> may observe.<Transactions in the PostgreSQL documentation>[version 18, section 3.4, all-or-nothing updates, permanent recording and visibility]{ref}
For example, transferring seven units from an account with balance twenty to one with balance five should produce balances thirteen and twelve. A failure after only the debit must not leave thirteen and five as a completed transfer. In <SQL>, a transaction block uses `BEGIN`, then the related updates, then `COMMIT`; `ROLLBACK` abandons the uncommitted changes.<Transactions in the PostgreSQL documentation>[version 18, section 3.4, BEGIN, COMMIT and ROLLBACK]{ref}
Isolation is a separate question from grouping statements. Two concurrent transfers can each read an old balance before either writes. A correct application must select suitable <transaction isolation> or locking and handle possible conflicts; merely putting the statements in a <database transaction> does not establish every desired invariant. The corresponding <database schedule> records their interleaving.
Back to article page