Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nIXrt-0008QJ-2e for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Feb 2022 15:29:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nIXrr-0000LR-Ky for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Feb 2022 15:29:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nIXrr-0000LI-3Q for pgsql-hackers@lists.postgresql.org; Fri, 11 Feb 2022 15:29:51 +0000 Received: from mail-io1-xd32.google.com ([2607:f8b0:4864:20::d32]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nIXro-00086O-Gn for pgsql-hackers@postgresql.org; Fri, 11 Feb 2022 15:29:50 +0000 Received: by mail-io1-xd32.google.com with SMTP id q204so11773349iod.8 for ; Fri, 11 Feb 2022 07:29:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=mD4WKtmjUqFU9WBSl0UzkGgbQtMspSinIQnhk/lMNeQ=; b=Elne/yIpTyCqO872TauxhK7zTx/XxzfN1kKhv8BFtL8Gu7B5+to1IHhbOgjJX0rbQC rDRQBJ4IeTr0PSKC/bcbagMCrVAzoN+SVxcDoo8ouKQsCocDDIYqqXEaksmJBm9XYvYl RFEERxYwTjaGg7IubkAAvZ7T8NnZvfkzZIn8ADlx2ionI0bh2GWIYkw4Y9L+IG16mZ6o HgqlNS/Snzx9iJBNYBFU/6EWFdVl06ETLd+SeY4UXmLii5ZY1sO9t6UA5lXYzeUrCJo9 d1WbDuDtazcyWe7+yBD5nCGz3zRff3X4RfbmLdFXVisH0nWbhqp9ygVn05FBlvNLW+JP Gjlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=mD4WKtmjUqFU9WBSl0UzkGgbQtMspSinIQnhk/lMNeQ=; b=mA9xjxd83ylp07/zF6HVytATbjQZwXYJIs2bjFjOqHg9lEUDJF2jFBlWiIlKMf5LiY lrEFJnL7oJU2I9lA7rdm8SkBRA213TRv9kh5PLki75UV/Gs9rEcGYGKNYG/HEQ64Nx/j C1tgHr8G0JS2Prz6T9d1L5J5gEhp9bDlmypbMy+ZqiFybbgtT9GuPpL/kmUKi6OTDHQl HfBU+dWTDTH52ZaNM7FUPdHMH8DxznsLPMgvRiEU3Xmmsy0slPp3tfuoAo4IdgOv6qd4 XGv522uMdVJbUtB2l6nzTvJJF0Wy8WnsYrHGO1L9zX/eEPkm3GCr2q0ZO8S624sPwWd6 HXXg== X-Gm-Message-State: AOAM531u0giGiTSCrlzUqnQiBExftk5EO8OqWSndTnhCZbCjKcHWmn37 MDyFJSVfJnQmrJm3lYecW21FPA== X-Google-Smtp-Source: ABdhPJzEx8LOV9fsbL/Md9hPhB1Jg2DgJ1OPaR/JUtUoB9fcI1/61pRCFGUkox7MPKJzHrpmj3Lsdw== X-Received: by 2002:a05:6602:1302:: with SMTP id h2mr1157252iov.65.1644593386043; Fri, 11 Feb 2022 07:29:46 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id d2sm6080073iog.42.2022.02.11.07.29.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Feb 2022 07:29:45 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id BCAB4800A8D; Fri, 11 Feb 2022 09:29:44 -0600 (CST) Date: Fri, 11 Feb 2022 09:29:44 -0600 From: Justin Pryzby To: Jeevan Ladhe Cc: Robert Haas , Dipesh Pandit , Abhijit Menon-Sen , Dmitry Dolgov <9erthalion6@gmail.com>, Jeevan Ladhe , Mark Dilger , pgsql-hackers@postgresql.org, tushar Subject: Re: refactoring basebackup.c Message-ID: <20220211152944.GD31460@telsasoft.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Feb 11, 2022 at 08:35:25PM +0530, Jeevan Ladhe wrote: > Thanks Robert for the bravity :-) FYI: there's a couple typos in the last 2 patches. I added them to my typos branch; feel free to wait until April if you'd prefer to see them fixed in bulk. diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml index 53aa40dcd19..649b91208f3 100644 --- a/doc/src/sgml/ref/pg_basebackup.sgml +++ b/doc/src/sgml/ref/pg_basebackup.sgml @@ -419,7 +419,7 @@ PostgreSQL documentation The compression method can be set to gzip or lz4, or none for no - compression. A compression level can be optionally specified, by + compression. A compression level can optionally be specified, by appending the level number after a colon (:). If no level is specified, the default compression level will be used. If only a level is specified without mentioning an algorithm, @@ -440,7 +440,7 @@ PostgreSQL documentation -Xstream, pg_wal.tar will be compressed using gzip if client-side gzip compression is selected, but will not be compressed if server-side - compresion or LZ4 compresion is selected. + compression or LZ4 compression is selected.