@@ -2242,6 +2242,13 @@ BACKUP INSTANCE 'node'
2242
2242
<literal >MERGING</literal > — the backup is being merged.
2243
2243
</para >
2244
2244
</listitem >
2245
+ <listitem >
2246
+ <para >
2247
+ <literal >MERGED</literal > — the backup data files were
2248
+ successfully merged, but its metadata is in the process
2249
+ of been updated. Only full backup can have this status.
2250
+ </para >
2251
+ </listitem >
2245
2252
<listitem >
2246
2253
<para >
2247
2254
<literal >DELETING</literal > — the backup files are being deleted.
@@ -3146,7 +3153,9 @@ pg_probackup merge -B <replaceable>backup_dir</replaceable> --instance <replacea
3146
3153
<para >
3147
3154
This command merges the specified incremental backup to its
3148
3155
parent full backup, together with all incremental backups
3149
- between them. Once the merge is complete, the incremental
3156
+ between them. If the specified backup ID belong to the full backup,
3157
+ then it will be merged with the closest incremental backup.
3158
+ Once the merge is complete, the incremental
3150
3159
backups are removed as redundant. Thus, the merge operation is
3151
3160
virtually equivalent to retaking a full backup and removing all
3152
3161
the outdated backups, but it allows to save much time,
@@ -3165,7 +3174,8 @@ pg_probackup show -B <replaceable>backup_dir</replaceable> --instance <replaceab
3165
3174
</programlisting >
3166
3175
<para >
3167
3176
If the merge is still in progress, the backup status is
3168
- displayed as <literal >MERGING</literal >. The merge is idempotent, so you can
3177
+ displayed as <literal >MERGING</literal > or, at the final stage,
3178
+ <literal >MERGED</literal >. The merge is idempotent, so you can
3169
3179
restart the merge if it was interrupted.
3170
3180
</para >
3171
3181
</refsect2 >
@@ -3404,6 +3414,7 @@ pg_probackup backup -B <replaceable>backup_dir</replaceable> -b <replaceable>bac
3404
3414
[--no-validate] [--skip-block-validation]
3405
3415
[-w --no-password] [-W --password]
3406
3416
[--archive-timeout=<replaceable >timeout</replaceable >] [--external-dirs=<replaceable >external_directory_path</replaceable >]
3417
+ [--no-sync]
3407
3418
[<replaceable >connection_options</replaceable >] [<replaceable >compression_options</replaceable >] [<replaceable >remote_options</replaceable >]
3408
3419
[<replaceable >retention_options</replaceable >] [<replaceable >pinning_options</replaceable >] [<replaceable >logging_options</replaceable >]
3409
3420
</programlisting >
@@ -3556,6 +3567,18 @@ pg_probackup backup -B <replaceable>backup_dir</replaceable> -b <replaceable>bac
3556
3567
</para >
3557
3568
</listitem >
3558
3569
</varlistentry >
3570
+
3571
+ <varlistentry >
3572
+ <term ><option >--no-sync</option ></term >
3573
+ <listitem >
3574
+ <para >
3575
+ Do not sync backed up files to disk. You can use this flag to speed
3576
+ up backup process. Using this flag can result in data
3577
+ corruption in case of operating system or hardware crash.
3578
+ Corruption can be detected by backup validation.
3579
+ </para >
3580
+ </listitem >
3581
+ </varlistentry >
3559
3582
</variablelist >
3560
3583
</para >
3561
3584
@@ -3583,7 +3606,7 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
3583
3606
[-j <replaceable >num_threads</replaceable >] [--progress]
3584
3607
[-T <replaceable >OLDDIR</replaceable >=<replaceable >NEWDIR</replaceable >] [--external-mapping=<replaceable >OLDDIR</replaceable >=<replaceable >NEWDIR</replaceable >] [--skip-external-dirs]
3585
3608
[-R | --restore-as-replica] [--no-validate] [--skip-block-validation] [--force]
3586
- [--restore-command=<replaceable >cmdline</replaceable >]
3609
+ [--restore-command=<replaceable >cmdline</replaceable >] [--no-sync]
3587
3610
[<replaceable >recovery_target_options</replaceable >] [<replaceable >logging_options</replaceable >] [<replaceable >remote_options</replaceable >]
3588
3611
[<replaceable >partial_restore_options</replaceable >] [<replaceable >remote_wal_archive_options</replaceable >]
3589
3612
</programlisting >
@@ -3705,6 +3728,17 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
3705
3728
</para >
3706
3729
</listitem >
3707
3730
</varlistentry >
3731
+
3732
+ <varlistentry >
3733
+ <term ><option >--no-sync</option ></term >
3734
+ <listitem >
3735
+ <para >
3736
+ Do not sync restored files to disk. You can use this flag to speed
3737
+ up restore process. Using this flag can result in data
3738
+ corruption in case of operating system or hardware crash.
3739
+ </para >
3740
+ </listitem >
3741
+ </varlistentry >
3708
3742
</variablelist >
3709
3743
</para >
3710
3744
<para >
@@ -3831,7 +3865,9 @@ pg_probackup merge -B <replaceable>backup_dir</replaceable> --instance <replacea
3831
3865
<para >
3832
3866
Merges the specified incremental backup to its parent full
3833
3867
backup, together with all incremental backups between them, if
3834
- any. As a result, the full backup takes in all the merged
3868
+ any. If the specified backup ID belong to the full backup,
3869
+ then it will be merged with the closest incremental backup.
3870
+ As a result, the full backup takes in all the merged
3835
3871
data, and the incremental backups are removed as redundant.
3836
3872
</para >
3837
3873
<para >
0 commit comments