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 1lEoyr-0004eF-Fg for pgsql-hackers@arkaria.postgresql.org; Wed, 24 Feb 2021 07:53:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lEoyq-0001my-Di for pgsql-hackers@arkaria.postgresql.org; Wed, 24 Feb 2021 07:53:08 +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 1lEoyq-0001mr-6P for pgsql-hackers@lists.postgresql.org; Wed, 24 Feb 2021 07:53:08 +0000 Received: from mail-il1-x12b.google.com ([2607:f8b0:4864:20::12b]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lEoyn-0004Gb-OR for pgsql-hackers@postgresql.org; Wed, 24 Feb 2021 07:53:07 +0000 Received: by mail-il1-x12b.google.com with SMTP id o1so931640ila.11 for ; Tue, 23 Feb 2021 23:53:05 -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=8D6UW4jLG2qrQK41FPRWkri/fteOUW5xOCrXFIKEBEk=; b=PaHIa6Jyr/dMnlHbrecIycJ3BWewjgH+bMbeBpcnvOnzX3+u3FhvurZtATegg4Gwcm 5yepzybuL68Ad3DlQ/irQx4xaVcv7wSYAwRGN4r6Jajn0LtXhC7oIf3ehc/v3GkV8/ej yViYbCb49wLexTES1fgjixDCfw3jgzIXJ/j7ykK3Y5TuvFismp34YIxkb34vO5lorPZL lMR6LZBXbwu/hOOWXUzYn1BKHiUN9rbVPhD26n+erSBF7Nne0cTmpayJLp5uJzgA88EI rchwKrQSlIxL6eAGfLHThbD35zhkPOpBiUtWN/e3rQBeB1s3exUnlYD2EUwc1N+PYm/c jCMg== 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=8D6UW4jLG2qrQK41FPRWkri/fteOUW5xOCrXFIKEBEk=; b=GB+5BCMNRUKMw7elzjPAK0rpAYzxMcl9pRr4Qy4k0ePOAnfb2AIILKv1CiGaI9wNco lCn/sMAXMpLrnj9/DsR70aYUZ4Mv6CW59lBK+7bqUJBmy0UxIJ2i3dlFGkHR55HSQ9tO c+UUuBmXX5g3xN63FECoi9FQOb8ZbntWpcurWuIitQYGVf/fIdzvtbnzlinDOXUSegzB rayhhNQRm5PL0I32wMAjszB7CwUf58dDclNRcbjbCa86me0oIm3l6FgwpnRBHG7yvRBM sG/XwR/Ii2tpiUfqejVAR9ENymeRcfkGir9B5+LPQ6ETDGpPkO5HG2GBiqC9OyBd74gv kYVw== X-Gm-Message-State: AOAM5310a+FQ9LbcyWKI0qrfDjijkg3Py4KTeG74Ey/6OO6Bu8DzwOAx SqSSIGEiXQrA/9WTgG7L31fX1w== X-Google-Smtp-Source: ABdhPJzm9bS/me+kkymdwcXaJBYceD+dz9pWAX6d7XqqvS7DPuytg9VLFjDfeKGgMntFkHfN4cm9Ew== X-Received: by 2002:a05:6e02:1a0f:: with SMTP id s15mr24111828ild.244.1614153184963; Tue, 23 Feb 2021 23:53:04 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id e12sm1210237ilm.85.2021.02.23.23.53.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Feb 2021 23:53:04 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 5FA60800941; Wed, 24 Feb 2021 01:53:03 -0600 (CST) Date: Wed, 24 Feb 2021 01:53:03 -0600 From: Justin Pryzby To: Matthias van de Meent Cc: Michael Paquier , Bharath Rupireddy , Tomas Vondra , Josef =?utf-8?B?xaBpbcOhbmVr?= , PostgreSQL Hackers Subject: Re: Improvements and additions to COPY progress reporting Message-ID: <20210224075303.GI14772@telsasoft.com> References: <0eb0a7e5-031d-51b6-b1c7-9804915d44f2@enterprisedb.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: Precedence: bulk On Sun, Feb 21, 2021 at 08:10:09PM +0100, Matthias van de Meent wrote: > Subject: [PATCH v9 1/3] Add progress-reported components for COPY progress > reporting > /* Increment amount of processed tuples and update the progress */ > /* Increment amount of processed tuples and update the progress */ Ideally, this would say "number of processed tuples" > Subject: [PATCH v9 2/3] Add backlinks to progress reporting documentation I think these should say that they report their progress *in* the view (not "to"): > + Each backend running ANALYZE will report its progress to > + the pg_stat_progress_analyze view. See > + Each backend running CLUSTER will report its progress to > + the pg_stat_progress_cluster view. See > + Each backend running COPY will report its progress to > + the pg_stat_progress_copy view. See > + Each backend running CREATE INDEX will report its > + progress to the pg_stat_progress_create_index > + Each backend running REINDEX will report its progress > + to the pg_stat_progress_create_index view. See Like this one: > + Each backend running VACUUM without the > + FULL option will report its progress in the I'm sorry I didn't include that in last week's message. You could also write: |"The progress of each backend running >ANALYZE< is reported in the >pg_stat_progress_analyze< view." Looking at the existing docs: https://www.postgresql.org/docs/devel/progress-reporting.html#COPY-PROGRESS-REPORTING | OID of the table on which the COPY command is executed Maybe it should say ".. is executing". Or ".. being executed": | OID of the table on which the COPY command is being executed -- Justin