@@ -417,30 +417,33 @@ PostgreSQL documentation
417
417
specify <literal>-Xfetch</literal>.
418
418
</para>
419
419
<para>
420
- The compression method can be set to <literal>gzip</literal> or
421
- <literal>lz4</literal>, or <literal>none</literal> for no
422
- compression. A compression level can be optionally specified, by
423
- appending the level number after a colon (<literal>:</literal>). If no
424
- level is specified, the default compression level will be used. If
425
- only a level is specified without mentioning an algorithm,
426
- <literal>gzip</literal> compression will be used if the level is
427
- greater than 0, and no compression will be used if the level is 0.
428
- </para>
429
- <para>
430
- When the tar format is used with <literal>gzip</literal> or
431
- <literal>lz4</literal>, the suffix <filename>.gz</filename> or
432
- <filename>.lz4</filename> will automatically be added to all tar
433
- filenames. When the plain format is used, client-side compression may
434
- not be specified, but it is still possible to request server-side
435
- compression. If this is done, the server will compress the backup for
436
- transmission, and the client will decompress and extract it.
420
+ The compression method can be set to <literal>gzip</literal>,
421
+ <literal>lz4</literal>, <literal>zstd</literal>, or
422
+ <literal>none</literal> for no compression. A compression level can
423
+ optionally be specified, by appending the level number after a colon
424
+ (<literal>:</literal>). If no level is specified, the default
425
+ compression level will be used. If only a level is specified without
426
+ mentioning an algorithm, <literal>gzip</literal> compression will be
427
+ used if the level is greater than 0, and no compression will be used if
428
+ the level is 0.
429
+ </para>
430
+ <para>
431
+ When the tar format is used with <literal>gzip</literal>,
432
+ <literal>lz4</literal>, or <literal>zstd</literal>, the suffix
433
+ <filename>.gz</filename>, <filename>.lz4</filename>, or
434
+ <filename>.zst</filename>, respectively, will be automatically added to
435
+ all tar filenames. When the plain format is used, client-side
436
+ compression may not be specified, but it is still possible to request
437
+ server-side compression. If this is done, the server will compress the
438
+ backup for transmission, and the client will decompress and extract it.
437
439
</para>
438
440
<para>
439
441
When this option is used in combination with
440
442
<literal>-Xstream</literal>, <literal>pg_wal.tar</literal> will
441
443
be compressed using <literal>gzip</literal> if client-side gzip
442
- compression is selected, but will not be compressed if server-side
443
- compresion or LZ4 compresion is selected.
444
+ compression is selected, but will not be compressed if any other
445
+ compression algorithm is selected, or if server-side compression
446
+ is selected.
444
447
</para>
445
448
</listitem>
446
449
</varlistentry>
0 commit comments