summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/db/transactions.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index 40a36e777d..44a21e5ee2 100644
--- a/docs/topics/db/transactions.txt
+++ b/docs/topics/db/transactions.txt
@@ -369,8 +369,8 @@ etc.), this should be fine. If it's not (if your follow-up action is so
critical that its failure should mean the failure of the transaction itself),
then you don't want to use the :func:`on_commit` hook. Instead, you may want
`two-phase commit`_ such as the :ref:`psycopg Two-Phase Commit protocol support
-<psycopg2:tpc>` and the `optional Two-Phase Commit Extensions in the Python
-DB-API specification`_.
+<psycopg2:tpc>` and the :pep:`optional Two-Phase Commit Extensions in the
+Python DB-API specification <249#optional-two-phase-commit-extensions>`.
Callbacks are not run until autocommit is restored on the connection following
the commit (because otherwise any queries done in a callback would open an
@@ -387,7 +387,6 @@ autocommit is disabled and you are not within an atomic block will result in an
error.
.. _two-phase commit: https://en.wikipedia.org/wiki/Two-phase_commit_protocol
-.. _optional Two-Phase Commit Extensions in the Python DB-API specification: https://www.python.org/dev/peps/pep-0249/#optional-two-phase-commit-extensions
Use in tests
------------