Knowledge base

repair-database verifiedcriticalWritten by the Hub

Create or upgrade the cluster schema

Creates missing tables and brings an existing schema up to the version the binary expects, then exits.

In detail

This is the step between having a database and having a MailerQ cluster: the engine writes its 33 tables itself. Hub's installer runs it right after generating the configuration and before starting the service, which is the required order — the command reads database-address from the configuration, so a config without a working database connection makes it fail. It is additive rather than destructive: an existing schema is upgraded, existing rows are kept. That distinction from –purge-database is the whole reason both exist, and it is worth being loud about, because the names are similar and one of them is irreversible.

What happens if you get it wrong

Run before the configuration names a reachable database.The command fails and the installation stops at a clear point rather than starting a broken node.verified by experiment · inference