Commit7ceb6fb

committed

doc: Clarify some wording in PL/pgSQL about transactions

Some text was still claiming that committing transactions was notpossible in PL/pgSQL.

1 parent0a63f99 commit7ceb6fbCopy full SHA for 7ceb6fb

File tree

-4

lines changed

-4

lines changed

Lines changed: 3 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -305,10 +305,9 @@ $$ LANGUAGE plpgsql;`
`305`	`305`	`for transaction`
`306`	`306`	`control. <application>PL/pgSQL</application>'s <command>BEGIN</command>/<command>END</command>`
`307`	`307`	`are only for grouping; they do not start or end a transaction.`
`308`		`- Functions are always executed within a transaction`
`309`		`- established by an outer query — they cannot start or commit that`
`310`		`- transaction, since there would be no context for them to execute in.`
`311`		`- However, a block containing an <literal>EXCEPTION</literal> clause effectively`
	`308`	`+ See <xref linkend="plpgsql-transactions"/> for information on managing`
	`309`	`+ transactions in <application>PL/pgSQL</application>.`
	`310`	`+ Also, a block containing an <literal>EXCEPTION</literal> clause effectively`
`312`	`311`	`forms a subtransaction that can be rolled back without affecting the`
`313`	`312`	`outer transaction. For more about that see <xref`
`314`	`313`	`linkend="plpgsql-error-trapping"/>.`

Comments

(0)