Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 9587b75

Browse filesBrowse files
indrupspostgres-dev
authored andcommitted
A few documentation edits
1 parent 36b9761 commit 9587b75
Copy full SHA for 9587b75

File tree

Expand file treeCollapse file tree

1 file changed

+6
-5
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+6
-5
lines changed
Open diff view settings
Collapse file

‎doc/pgprobackup.xml‎

Copy file name to clipboardExpand all lines: doc/pgprobackup.xml
+6-5Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2434,7 +2434,8 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
24342434
<para>
24352435
In addition to SSH connection, <application>pg_probackup</application> uses
24362436
a regular connection to the database to manage the remote operation.
2437-
See <xref linkend="pbk-configuring-the-database-cluster"/> for details of how to set up
2437+
See the section <link linkend="pbk-configuring-the-database-cluster">Configuring
2438+
the Database Cluster</link> for details of how to set up
24382439
a database connection.
24392440
</para>
24402441
</note>
@@ -3941,7 +3942,7 @@ pg_probackup delete -B <replaceable>backup_dir</replaceable> --instance <replace
39413942

39423943
<para>
39433944
To prepare for cloning/synchronizing a <productname>PostgreSQL</productname> instance,
3944-
set up the source instance server as follows:
3945+
set up the source server as follows:
39453946
<itemizedlist>
39463947
<listitem>
39473948
<para>
@@ -3964,7 +3965,7 @@ pg_probackup delete -B <replaceable>backup_dir</replaceable> --instance <replace
39643965

39653966
<para>
39663967
Before cloning/synchronizing a <productname>PostgreSQL</productname> instance, ensure that the source
3967-
instance server is running and accepting connections. To clone/sync a <productname>PostgreSQL</productname> instance,
3968+
server is running and accepting connections. To clone/sync a <productname>PostgreSQL</productname> instance,
39683969
on the server with the destination instance, you can run
39693970
the <xref linkend="pbk-catchup"/> command as follows:
39703971
</para>
@@ -4007,7 +4008,7 @@ pg_probackup catchup -b <replaceable>catchup_mode</replaceable> --source-pgdata=
40074008
By specifying the <option>--stream</option> option, you can set
40084009
<link linkend="pbk-stream-mode">STREAM</link> WAL delivery mode
40094010
of copying, which will include all the necessary WAL files by streaming them from
4010-
the instance server via replication protocol.
4011+
the server via replication protocol.
40114012
</para>
40124013
<para>
40134014
You can use <link linkend="pbk-connection-opts">connection_options</link> to specify
@@ -4998,7 +4999,7 @@ pg_probackup catchup -b <replaceable>catchup_mode</replaceable>
49984999
<para>
49995000
Copies the instance in <link linkend="pbk-stream-mode">STREAM</link> WAL delivery mode,
50005001
including all the necessary WAL files by streaming them from
5001-
the instance server via replication protocol.
5002+
the server via replication protocol.
50025003
</para>
50035004
</listitem>
50045005
</varlistentry>

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.