From a14b88819a8a22da4f5abb19a3b1b61aebb10a7c Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:20 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/plpython-subtransaction.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/plpython-subtransaction.html') diff --git a/doc/src/sgml/html/plpython-subtransaction.html b/doc/src/sgml/html/plpython-subtransaction.html index 73ee1fa..ce2637e 100644 --- a/doc/src/sgml/html/plpython-subtransaction.html +++ b/doc/src/sgml/html/plpython-subtransaction.html @@ -1,5 +1,5 @@ -46.7. Explicit Subtransactions
46.7. Explicit Subtransactions
Prev UpChapter 46. PL/Python — Python Procedural LanguageHome Next

46.7. Explicit Subtransactions

46.7.1. Subtransaction Context Managers

+46.7. Explicit Subtransactions

46.7. Explicit Subtransactions
Prev UpChapter 46. PL/Python — Python Procedural LanguageHome Next

46.7. Explicit Subtransactions

46.7.1. Subtransaction Context Managers

Recovering from errors caused by database access as described in Section 46.6.2 can lead to an undesirable situation where some operations succeed before one of them fails, @@ -65,4 +65,4 @@ $$ LANGUAGE plpython3u; database access. A regular Python exception raised inside an explicit subtransaction block would also cause the subtransaction to be rolled back. -

Prev Up Next
46.6. Database Access Home 46.8. Transaction Management
\ No newline at end of file +

Prev Up Next
46.6. Database Access Home 46.8. Transaction Management
\ No newline at end of file -- cgit v1.2.3