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 1lHqql-0007qc-Ny for pgsql-hackers@arkaria.postgresql.org; Thu, 04 Mar 2021 16:29:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lHqqk-0005F1-AS for pgsql-hackers@arkaria.postgresql.org; Thu, 04 Mar 2021 16:29:18 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lHqqj-0005Dk-Vc for pgsql-hackers@lists.postgresql.org; Thu, 04 Mar 2021 16:29:18 +0000 Received: from mail-qk1-x732.google.com ([2607:f8b0:4864:20::732]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lHqqh-0005c0-9M for pgsql-hackers@postgresql.org; Thu, 04 Mar 2021 16:29:16 +0000 Received: by mail-qk1-x732.google.com with SMTP id z190so28363320qka.9 for ; Thu, 04 Mar 2021 08:29:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Zy63TywYYTAnDiDs+Hyx2gV9KXtXNuKJxD9FW1rLeLA=; b=LlC/KYTBoN7IAlNSLS73aeP5DQLCnPzyfrWqHN/BhAtncfR5XNdMoMV8+QsU6kUoBa HQEE/4N7zWMzEcqpR91A3C8ov3osFBIyKaklXMR7MxG+GAZqUBZhUCnHTNrVmaD2RyQV CDCppYKGkjuF7duUcPpHlEKBEwXmJbYOv0PzA69Y0PN8zb8Xds1DpCBKBXzzth9MVfqD tGTT3oj3JQ/jgNWoN+QpbPkd8s9WdBPG4CKhrQsOpF7XyMSYEhrhzVWy9FsluCndVSLA iILRWhhC+WXjxMqfgnwydJkTRXj5SHKyFJl125v5HrSSp7eid0qdRU0jLMMuoj7ILf+N B4Ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Zy63TywYYTAnDiDs+Hyx2gV9KXtXNuKJxD9FW1rLeLA=; b=qzV11TXWZOatsBpYPdMN4que3VfthbHezoemJb3CRF+jc/0vfjL0yho3vMYhLAxvVj lMcw7NkXUukrJjX1/Nh9kds/0X1eP8ftsE/UB5KWUlFODdzC4rxdGK6s0rCIC/Lhm7M1 2Q99xWBLDUui5TeBKHcTwgg6jVM7SnAfM67d6YLVgjgRZkm6Z9A7aC8C8y1suO16RKkk IzzOmcpK3xzPqFoiNw9ucs2h+9buerNAGh9DNlV3O734x7Rhvugp+8V65dKrsRO5BXij /ot8HCh4yzPC+rjorYaf+QaPv1tv3yubrLVEjN5NMgowMgOGr/jk1y8iOYiAlIrx5SRM iUcg== X-Gm-Message-State: AOAM5315jvCPeQw/TDhORQZsMTq8CtjBSXoaxdFC3RL086VYer62QqkD IKuOOfhRpJeUdX/PW4lrEIYB4w== X-Google-Smtp-Source: ABdhPJzZDc0tG7m+/CujcJiBcZuQFe6xplsBa1fEiDlzhU+yVK67r+DEcpY+dAqlJJ/ZSw48GQ1LxQ== X-Received: by 2002:a37:ef14:: with SMTP id j20mr2501544qkk.471.1614875354290; Thu, 04 Mar 2021 08:29:14 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id u35sm37628qtb.18.2021.03.04.08.29.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Mar 2021 08:29:13 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 94942800A3A; Thu, 4 Mar 2021 10:29:12 -0600 (CST) Date: Thu, 4 Mar 2021 10:29:12 -0600 From: Justin Pryzby To: Matthias van de Meent Cc: Bharath Rupireddy , Michael Paquier , Tomas Vondra , Josef =?utf-8?B?xaBpbcOhbmVr?= , pgsql-hackers@postgresql.org Subject: Re: Improvements and additions to COPY progress reporting Message-ID: <20210304162912.GO29832@telsasoft.com> References: <20210224075303.GI14772@telsasoft.com> 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 Thu, Mar 04, 2021 at 05:19:18PM +0100, Matthias van de Meent wrote: > On Thu, 4 Mar 2021 at 13:36, Bharath Rupireddy wrote: > > > > + > > + Each backend running VACUUM without the > > + FULL option will report its progress in the > > + pg_stat_progress_vacuum view. Backends running > > + VACUUM with the FULL option report > > + progress in the pg_stat_progress_cluster view > > + instead. See and > > + for details. > > + > > > > I think a typo, missing "will" between option and report - it's "with > > the FULL option will report" > > "Backends running [...] report progress to [...] instead" is, > a.f.a.i.k., correct English. Adding 'will' would indeed still be > correct, but it would in my opinion also be decremental to the > readability of the section due to the repeated use of the same > template sentence structure. I think that keeping it as-is is just > fine. I'd prefer to see the same thing repeated, since then it's easy to compare, for readers, and also future doc authors. That's normal in technical documentation to have redundancy. It's easy to read. I'd suggest to move "instead" into the middle of the sentence, and combine VACUUM+FULL, and add "their": > > + ... Backends running VACUUM FULL will instead report > > + their progress in the pg_stat_progress_cluster view. -- Justin