@@ -1634,13 +1634,14 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
1634
1634
<para >
1635
1635
If you restore <link linkend =" pbk-archive-mode" >ARCHIVE</link > backups,
1636
1636
perform <link linkend =" pbk-performing-point-in-time-pitr-recovery" >PITR</link >,
1637
- or specify the <literal >--restore-as-replica</literal > option with the
1637
+ or specify the <literal >--restore-as-replica</literal > flag with the
1638
1638
<literal >restore</literal > command to set up a standby server,
1639
1639
<application >pg_probackup</application > creates a recovery configuration
1640
1640
file once all data files are copied into the target directory. This file
1641
1641
includes the minimal settings required for recovery, except for the password in the
1642
1642
<ulink url =" https://postgrespro.com/docs/postgresql/current/runtime-config-replication.html#GUC-PRIMARY-CONNINFO" >primary_conninfo</ulink >
1643
- parameter; you have to add the password manually, if required.
1643
+ parameter; you have to add the password manually or use
1644
+ the <literal >--primary-conninfo</literal > option, if required.
1644
1645
For <productname >PostgreSQL</productname > 11 or lower,
1645
1646
recovery settings are written into the <filename >recovery.conf</filename >
1646
1647
file. Starting from <productname >PostgreSQL</productname > 12,
@@ -2242,6 +2243,13 @@ BACKUP INSTANCE 'node'
2242
2243
<literal >MERGING</literal > — the backup is being merged.
2243
2244
</para >
2244
2245
</listitem >
2246
+ <listitem >
2247
+ <para >
2248
+ <literal >MERGED</literal > — the backup data files were
2249
+ successfully merged, but its metadata is in the process
2250
+ of been updated. Only full backup can have this status.
2251
+ </para >
2252
+ </listitem >
2245
2253
<listitem >
2246
2254
<para >
2247
2255
<literal >DELETING</literal > — the backup files are being deleted.
@@ -3146,7 +3154,9 @@ pg_probackup merge -B <replaceable>backup_dir</replaceable> --instance <replacea
3146
3154
<para >
3147
3155
This command merges the specified incremental backup to its
3148
3156
parent full backup, together with all incremental backups
3149
- between them. Once the merge is complete, the incremental
3157
+ between them. If the specified backup ID belong to the full backup,
3158
+ then it will be merged with the closest incremental backup.
3159
+ Once the merge is complete, the incremental
3150
3160
backups are removed as redundant. Thus, the merge operation is
3151
3161
virtually equivalent to retaking a full backup and removing all
3152
3162
the outdated backups, but it allows to save much time,
@@ -3165,7 +3175,8 @@ pg_probackup show -B <replaceable>backup_dir</replaceable> --instance <replaceab
3165
3175
</programlisting >
3166
3176
<para >
3167
3177
If the merge is still in progress, the backup status is
3168
- displayed as <literal >MERGING</literal >. The merge is idempotent, so you can
3178
+ displayed as <literal >MERGING</literal > or, at the final stage,
3179
+ <literal >MERGED</literal >. The merge is idempotent, so you can
3169
3180
restart the merge if it was interrupted.
3170
3181
</para >
3171
3182
</refsect2 >
@@ -3404,6 +3415,7 @@ pg_probackup backup -B <replaceable>backup_dir</replaceable> -b <replaceable>bac
3404
3415
[--no-validate] [--skip-block-validation]
3405
3416
[-w --no-password] [-W --password]
3406
3417
[--archive-timeout=<replaceable >timeout</replaceable >] [--external-dirs=<replaceable >external_directory_path</replaceable >]
3418
+ [--no-sync]
3407
3419
[<replaceable >connection_options</replaceable >] [<replaceable >compression_options</replaceable >] [<replaceable >remote_options</replaceable >]
3408
3420
[<replaceable >retention_options</replaceable >] [<replaceable >pinning_options</replaceable >] [<replaceable >logging_options</replaceable >]
3409
3421
</programlisting >
@@ -3556,6 +3568,18 @@ pg_probackup backup -B <replaceable>backup_dir</replaceable> -b <replaceable>bac
3556
3568
</para >
3557
3569
</listitem >
3558
3570
</varlistentry >
3571
+
3572
+ <varlistentry >
3573
+ <term ><option >--no-sync</option ></term >
3574
+ <listitem >
3575
+ <para >
3576
+ Do not sync backed up files to disk. You can use this flag to speed
3577
+ up backup process. Using this flag can result in data
3578
+ corruption in case of operating system or hardware crash.
3579
+ Corruption can be detected by backup validation.
3580
+ </para >
3581
+ </listitem >
3582
+ </varlistentry >
3559
3583
</variablelist >
3560
3584
</para >
3561
3585
@@ -3582,8 +3606,11 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
3582
3606
[--help] [-D <replaceable >data_dir</replaceable >] [-i <replaceable >backup_id</replaceable >]
3583
3607
[-j <replaceable >num_threads</replaceable >] [--progress]
3584
3608
[-T <replaceable >OLDDIR</replaceable >=<replaceable >NEWDIR</replaceable >] [--external-mapping=<replaceable >OLDDIR</replaceable >=<replaceable >NEWDIR</replaceable >] [--skip-external-dirs]
3585
- [-R | --restore-as-replica] [--no-validate] [--skip-block-validation] [--force]
3609
+ [-R | --restore-as-replica] [--no-validate] [--skip-block-validation]
3610
+ [--force] [--no-sync]
3611
+ [--restore-command=<replaceable >cmdline</replaceable >]
3586
3612
[--restore-command=<replaceable >cmdline</replaceable >]
3613
+ [--primary-conninfo=<replaceable >primary_conninfo</replaceable >]
3587
3614
[<replaceable >recovery_target_options</replaceable >] [<replaceable >logging_options</replaceable >] [<replaceable >remote_options</replaceable >]
3588
3615
[<replaceable >partial_restore_options</replaceable >] [<replaceable >remote_wal_archive_options</replaceable >]
3589
3616
</programlisting >
@@ -3621,6 +3648,21 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
3621
3648
</listitem >
3622
3649
</varlistentry >
3623
3650
3651
+ <varlistentry >
3652
+ <term ><option >--primary-conninfo=<replaceable >primary_conninfo</replaceable ></option ></term >
3653
+ <listitem >
3654
+ <para >
3655
+ Sets the
3656
+ <ulink url =" https://postgrespro.com/docs/postgresql/current/runtime-config-replication.html#GUC-PRIMARY-CONNINFO" >primary_conninfo</ulink >
3657
+ parameter to the specified value.
3658
+ This option will be ignored unless the <option >-R</option > flag if specified.
3659
+ </para >
3660
+ <para >
3661
+ Example: <literal >--primary-conninfo='host=192.168.1.50 port=5432 user=foo password=foopass'</literal >
3662
+ </para >
3663
+ </listitem >
3664
+ </varlistentry >
3665
+
3624
3666
<varlistentry >
3625
3667
<term ><option >-T <replaceable >OLDDIR</replaceable >=<replaceable >NEWDIR</replaceable ></option ></term >
3626
3668
<term ><option >--tablespace-mapping=<replaceable >OLDDIR</replaceable >=<replaceable >NEWDIR</replaceable ></option ></term >
@@ -3705,6 +3747,17 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
3705
3747
</para >
3706
3748
</listitem >
3707
3749
</varlistentry >
3750
+
3751
+ <varlistentry >
3752
+ <term ><option >--no-sync</option ></term >
3753
+ <listitem >
3754
+ <para >
3755
+ Do not sync restored files to disk. You can use this flag to speed
3756
+ up restore process. Using this flag can result in data
3757
+ corruption in case of operating system or hardware crash.
3758
+ </para >
3759
+ </listitem >
3760
+ </varlistentry >
3708
3761
</variablelist >
3709
3762
</para >
3710
3763
<para >
@@ -3831,7 +3884,9 @@ pg_probackup merge -B <replaceable>backup_dir</replaceable> --instance <replacea
3831
3884
<para >
3832
3885
Merges the specified incremental backup to its parent full
3833
3886
backup, together with all incremental backups between them, if
3834
- any. As a result, the full backup takes in all the merged
3887
+ any. If the specified backup ID belong to the full backup,
3888
+ then it will be merged with the closest incremental backup.
3889
+ As a result, the full backup takes in all the merged
3835
3890
data, and the incremental backups are removed as redundant.
3836
3891
</para >
3837
3892
<para >
0 commit comments