database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-21 12:05:57 +03:00
Code

Clarify terminology standalone backend vs. single-user mode

Browse Source 
Most of the documentation uses "single-user mode", so use that in the
code as well.  Adjust the documentation to match the new error message
wording.  Also add a documentation index entry for "single-user mode".

Based-on-patch-by: Jeff Janes <jeff.janes@gmail.com>
This commit is contained in:
Peter Eisentraut 2013-06-20 23:03:18 -04:00
parent 4c54e87a86
commit 7dfd5cd21c
3 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/maintenance.sgml
View File

@ -581,17 +581,17 @@ HINT: To avoid a database shutdown, execute a database-wide VACUUM in "mydb".
<programlisting> <programlisting>
ERROR: database is not accepting commands to avoid wraparound data loss in database "mydb" ERROR: database is not accepting commands to avoid wraparound data loss in database "mydb"
HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb". HINT: Stop the postmaster and vacuum that database in single-user mode.
</programlisting> </programlisting>
The 1-million-transaction safety margin exists to let the The 1-million-transaction safety margin exists to let the
administrator recover without data loss, by manually executing the administrator recover without data loss, by manually executing the
required <command>VACUUM</> commands. However, since the system will not required <command>VACUUM</> commands. However, since the system will not
execute commands once it has gone into the safety shutdown mode, execute commands once it has gone into the safety shutdown mode,
the only way to do this is to stop the server and use a single-user the only way to do this is to stop the server and start the server in single-user
backend to execute <command>VACUUM</>. The shutdown mode is not enforced mode to execute <command>VACUUM</>. The shutdown mode is not enforced
by a single-user backend. See the <xref linkend="app-postgres"> reference in single-user mode. See the <xref linkend="app-postgres"> reference
page for details about using a single-user backend. page for details about using single-user mode.
</para> </para>
</sect2> </sect2>

4
doc/src/sgml/ref/postgres-ref.sgml
View File

@ -529,6 +529,10 @@ PostgreSQL documentation
<refsect2> <refsect2>
<title>Options for Single-User Mode</title> <title>Options for Single-User Mode</title>
<indexterm>
<primary>single-user mode</primary>
</indexterm>
<para> <para>
The following options only apply to the single-user mode. The following options only apply to the single-user mode.
</para> </para>

6
src/backend/access/transam/varsup.c
View File

@ -73,7 +73,7 @@ GetNewTransactionId(bool isSubXact)
* If we're past xidVacLimit, start trying to force autovacuum cycles. * If we're past xidVacLimit, start trying to force autovacuum cycles.
* If we're past xidWarnLimit, start issuing warnings. * If we're past xidWarnLimit, start issuing warnings.
* If we're past xidStopLimit, refuse to execute transactions, unless * If we're past xidStopLimit, refuse to execute transactions, unless
* we are running in a standalone backend (which gives an escape hatch * we are running in single-user mode (which gives an escape hatch
* to the DBA who somehow got past the earlier defenses). * to the DBA who somehow got past the earlier defenses).
* *
* Note that this coding also appears in GetNewMultiXactId. * Note that this coding also appears in GetNewMultiXactId.
@ -114,14 +114,14 @@ GetNewTransactionId(bool isSubXact)
(errcode(ERRCODE_PROGRAM_LIMIT_EXCEEDED), (errcode(ERRCODE_PROGRAM_LIMIT_EXCEEDED),
errmsg("database is not accepting commands to avoid wraparound data loss in database \"%s\"", errmsg("database is not accepting commands to avoid wraparound data loss in database \"%s\"",
oldest_datname), oldest_datname),
errhint("Stop the postmaster and use a standalone backend to vacuum that database.\n" errhint("Stop the postmaster and vacuum that database in single-user mode.\n"
"You might also need to commit or roll back old prepared transactions."))); "You might also need to commit or roll back old prepared transactions.")));
else else
ereport(ERROR, ereport(ERROR,
(errcode(ERRCODE_PROGRAM_LIMIT_EXCEEDED), (errcode(ERRCODE_PROGRAM_LIMIT_EXCEEDED),
errmsg("database is not accepting commands to avoid wraparound data loss in database with OID %u", errmsg("database is not accepting commands to avoid wraparound data loss in database with OID %u",
oldest_datoid), oldest_datoid),
errhint("Stop the postmaster and use a standalone backend to vacuum that database.\n" errhint("Stop the postmaster and vacuum that database in single-user mode.\n"
"You might also need to commit or roll back old prepared transactions."))); "You might also need to commit or roll back old prepared transactions.")));
} }
else if (TransactionIdFollowsOrEquals(xid, xidWarnLimit)) else if (TransactionIdFollowsOrEquals(xid, xidWarnLimit))