Fix pg_basebackup so that it accepts 0 as a valid compression level.
authorFujii Masao
Mon, 1 Aug 2016 08:36:14 +0000 (17:36 +0900)
committerFujii Masao
Mon, 1 Aug 2016 08:37:18 +0000 (17:37 +0900)
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

doc/src/sgml/ref/pg_basebackup.sgml
src/bin/pg_basebackup/pg_basebackup.c

index 616c74a4bad6442e0f0cc029d96d1e52eb4ce928..0883277d84bde0761de79026ab0d8317730eff79 100644 (file)
@@ -343,7 +343,7 @@ PostgreSQL documentation
       
        
         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.
        
index 86e18f6e61b656f8deb275a0629bf32ef61691b1..84eef6466d7682224273ab178c62dc41ce16b7e4 100644 (file)
@@ -2050,7 +2050,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);