You've already forked pg_probackup
mirror of
https://github.com/postgrespro/pg_probackup.git
synced 2025-07-17 07:22:20 +02:00
Fix whitespaces and typos in documentation
The output of "show" command was incorrect as well.
This commit is contained in:
@ -130,12 +130,12 @@ Here are some commands to restore from a backup:
|
||||
=== SHOW A BACKUP ===
|
||||
|
||||
$ pg_arman show
|
||||
==================================================================================================
|
||||
Start Mode Current TLI Parent TLI Time Data WAL Log Backup Status
|
||||
==================================================================================================
|
||||
2013-12-25 03:02:31 INCR 1 0 0m 203kB 67MB ---- 67MB DONE
|
||||
2013-12-25 03:02:31 INCR 1 0 0m 0B ---- ---- 0B ERROR
|
||||
2013-12-25 03:02:25 FULL 1 0 0m 33MB 33MB ---- 64MB OK
|
||||
===================================================================================
|
||||
Start Mode Current TLI Parent TLI Time Data Backup Status
|
||||
===================================================================================
|
||||
2013-12-25 03:02:31 INCR 1 0 0m 203kB 67MB DONE
|
||||
2013-12-25 03:02:31 INCR 1 0 0m 0B 0B ERROR
|
||||
2013-12-25 03:02:25 FULL 1 0 0m 33MB 364MB OK
|
||||
|
||||
The fields are:
|
||||
|
||||
@ -241,8 +241,8 @@ The parameters whose name start are started with --recovery refer to
|
||||
the same parameters as the ones in recovery.confin recovery.conf.
|
||||
|
||||
*--recovery-target-timeline*=_TIMELINE_::
|
||||
Specifies recovering into a particular timeline.
|
||||
If not specified, the current timeline is used.
|
||||
Specifies recovering into a particular timeline. If not specified,
|
||||
the current timeline is used.
|
||||
|
||||
*--recovery-target-time*=_TIMESTAMP_::
|
||||
This parameter specifies the timestamp up to which recovery will
|
||||
@ -326,8 +326,6 @@ variables or in configuration file as follows:
|
||||
--validate VALIDATE Yes
|
||||
--keep-data-generations KEEP_DATA_GENERATIONS Yes
|
||||
--keep-data-days KEEP_DATA_DAYS Yes
|
||||
--keep-arclog-files KEEP_ARCLOG_FILES Yes
|
||||
--keep-arclog-days KEEP_ARCLOG_DAYS Yes
|
||||
--recovery-target-timeline RECOVERY_TARGET_TIMELINE Yes
|
||||
--recovery-target-xid RECOVERY_TARGET_XID Yes
|
||||
--recovery-target-time RECOVERY_TARGET_TIME Yes
|
||||
@ -338,7 +336,7 @@ of environment variables. The password can not be specified in command
|
||||
line and configuration file for security reason.
|
||||
|
||||
This utility, like most other PostgreSQL utilities, also uses the
|
||||
environment variables supported by libpq (see Environment Variables)
|
||||
environment variables supported by libpq (see Environment Variables).
|
||||
|
||||
== RESTRICTIONS ==
|
||||
|
||||
@ -394,7 +392,7 @@ pg_arman returns exit codes for each error status.
|
||||
26 ERROR_PID_BROKEN postmaster.pid is broken
|
||||
|
||||
== AUTHOR ==
|
||||
pg_arman is a fork of pg_rman that was originally written by NTT, now
|
||||
maintained by Michael Paquier.
|
||||
pg_arman is a fork of pg_rman that was originally written by NTT, now developed
|
||||
and maintained by Michael Paquier.
|
||||
|
||||
Please report bug reports at <https://github.com/michaelpq/pg_arman>.
|
||||
|
Reference in New Issue
Block a user