GNU/Linux |
CentOS 5.2 |
|
![]() |
start_transaction(7) |
![]() |
START TRANSACTION − start a transaction block
START TRANSACTION [ transaction_mode [, ...] ]
where transaction_mode is one of:
ISOLATION LEVEL
{ SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ
UNCOMMITTED }
READ WRITE | READ ONLY
This command begins a new transaction block. If the isolation level or read/write mode is specified, the new transaction has those characteristics, as if SET TRANSACTION [set_transaction(7)] was executed. This is the same as the BEGIN [begin(7)] command.
Refer to SET TRANSACTION [set_transaction(7)] for information on the meaning of the parameters to this statement.
In the standard, it is not necessary to issue START TRANSACTION to start a transaction block: any SQL command implicitly begins a block. PostgreSQL’s behavior can be seen as implicitly issuing a COMMIT after each command that does not follow START TRANSACTION (or BEGIN), and it is therefore often called ’’autocommit’’. Other relational database systems may offer an autocommit feature as a convenience.
The SQL standard requires commas between successive transaction_modes, but for historical reasons PostgreSQL allows the commas to be omitted.
See also the compatibility section of SET TRANSACTION [set_transaction(7)].
BEGIN [begin(7)], COMMIT [commit(l)], ROLLBACK [rollback(l)], SAVEPOINT [savepoint(l)], SET TRANSACTION [set_transaction(l)]
![]() |
start_transaction(7) | ![]() |