taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 1346b401d5b4df4b65ff58a61fc59046460705e4
parent 3e64e64098320fe121f503169432ada033d83fe3
Author: Florian Dold <dold@taler.net>
Date:   Tue,  8 Sep 2026 21:48:43 +0200

manpages: explain unfinished upgrades in operator terms

Diffstat:
Mmanpages/taler-auditor-dbinit.1.rst | 15+++++----------
Mmanpages/taler-exchange-dbinit.1.rst | 15+++++----------
Mmanpages/taler-merchant-dbinit.1.rst | 15+++++----------
3 files changed, 15 insertions(+), 30 deletions(-)

diff --git a/manpages/taler-auditor-dbinit.1.rst b/manpages/taler-auditor-dbinit.1.rst @@ -38,16 +38,11 @@ Normal initialization always executes ``versioning.sql`` under the migration lock. This script upgrades the shared ``_v`` metadata schema transactionally and records its revision in ``_v.versioning``. An already-current script leaves schema objects and metadata unchanged. A script with an older target -revision preserves a newer installed revision. All migration SQL runs on the -connection holding the migration lock, so losing that connection also stops -its writes. Pending finalization is recorded in ``_v.pending_finalizations`` -before applying migrations and cleared only when finalization commits. Failed -finalization remains visible to ``--dry``, even without procedure files. - -Normal service connections reject pending finalization for their own component -and failures to inspect that status. Administrative connections remain available -so dbinit can finish the migration. These are startup checks; stop the services -before running migrations. +revision preserves a newer installed revision. + +Stop the services before upgrading the database. If an upgrade fails, rerun +**taler-auditor-dbinit** to complete it before restarting the services. +Services refuse to start while the final upgrade steps are unfinished. Its options are as follows: diff --git a/manpages/taler-exchange-dbinit.1.rst b/manpages/taler-exchange-dbinit.1.rst @@ -41,16 +41,11 @@ Normal initialization always executes ``versioning.sql`` under the migration lock. This script upgrades the shared ``_v`` metadata schema transactionally and records its revision in ``_v.versioning``. An already-current script leaves schema objects and metadata unchanged. A script with an older target -revision preserves a newer installed revision. All migration SQL runs on the -connection holding the migration lock, so losing that connection also stops -its writes. Pending finalization is recorded in ``_v.pending_finalizations`` -before applying migrations and cleared only when finalization commits. Failed -finalization remains visible to ``--dry``, even without procedure files. - -Normal service connections reject pending finalization for their own component -and failures to inspect that status. Administrative connections remain available -so dbinit can finish the migration. These are startup checks; stop the services -before running migrations. +revision preserves a newer installed revision. + +Stop the services before upgrading the database. If an upgrade fails, rerun +**taler-exchange-dbinit** to complete it before restarting the services. +Services refuse to start while the final upgrade steps are unfinished. Its options are as follows: diff --git a/manpages/taler-merchant-dbinit.1.rst b/manpages/taler-merchant-dbinit.1.rst @@ -39,16 +39,11 @@ Normal initialization always executes ``versioning.sql`` under the migration lock. This script upgrades the shared ``_v`` metadata schema transactionally and records its revision in ``_v.versioning``. An already-current script leaves schema objects and metadata unchanged. A script with an older target -revision preserves a newer installed revision. All migration SQL runs on the -connection holding the migration lock, so losing that connection also stops -its writes. Pending finalization is recorded in ``_v.pending_finalizations`` -before applying migrations and cleared only when finalization commits. Failed -finalization remains visible to ``--dry``, even without procedure files. - -Normal service connections reject pending finalization for their own component -and failures to inspect that status. Administrative connections remain available -so dbinit can finish the migration. These are startup checks; stop the services -before running migrations. +revision preserves a newer installed revision. + +If an upgrade fails, rerun +**taler-merchant-dbinit** to complete it before restarting the services. +Services refuse to start while the final upgrade steps are unfinished. Its options are as follows: