Fix pg_basebackup so that it accepts 0 as a valid compression level.

The help message for pg_basebackup specifies that the numbers 0 through 9
are accepted as valid values of -Z option. But, previously -Z 0 was rejected
as an invalid compression level.

Per discussion, it's better to make pg_basebackup treat 0 as valid
compression level meaning no compression, like pg_dump.

Back-patch to all supported versions.

Reported-By: Jeff Janes
Reviewed-By: Amit Kapila
Discussion: CAMkU=1x+GwjSayc57v6w87ij6iRGFWt=hVfM0B64b1_bPVKRqg@mail.gmail.com

diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml
index ec2e702f7bc45459d5b967db418087ca792042a6..82aa43968e02e0877b39306ab5f6ca8b76135ff0 100644 (file)
--- a/doc/src/sgml/ref/pg_basebackup.sgml
+++ b/doc/src/sgml/ref/pg_basebackup.sgml
@@ -283,7 +283,7 @@ PostgreSQL documentation
       <listitem>
        <para>
         Enables gzip compression of tar file output, and specifies the
-        compression level (1 through 9, 9 being best
+        compression level (0 through 9, 0 being no compression and 9 being best
         compression). Compression is only available when using the tar
         format.
        </para>

diff --git a/src/bin/pg_basebackup/pg_basebackup.c b/src/bin/pg_basebackup/pg_basebackup.c
index e881d6192b7887a6c312d7187d68ddfd40f17b92..176101ffd154f1b5cfcead069e45d9891edffa7b 100644 (file)
--- a/src/bin/pg_basebackup/pg_basebackup.c
+++ b/src/bin/pg_basebackup/pg_basebackup.c
@@ -1789,7 +1789,7 @@ main(int argc, char **argv)
                                break;
                        case 'Z':
                                compresslevel = atoi(optarg);
-                               if (compresslevel <= 0 || compresslevel > 9)
+                               if (compresslevel < 0 || compresslevel > 9)
                                {
                                        fprintf(stderr, _("%s: invalid compression level \"%s\"\n"),
                                                        progname, optarg);