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 1kxJw3-0006kn-2u for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Jan 2021 01:17:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kxJvV-00059c-2o for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Jan 2021 01:17:21 +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 1kxJvU-00059V-L4 for pgsql-hackers@lists.postgresql.org; Thu, 07 Jan 2021 01:17:20 +0000 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kxJvR-00056q-3X for pgsql-hackers@lists.postgresql.org; Thu, 07 Jan 2021 01:17:19 +0000 Received: by mail-io1-xd33.google.com with SMTP id o6so4593945iob.10 for ; Wed, 06 Jan 2021 17:17:16 -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:content-transfer-encoding:in-reply-to :user-agent; bh=Pn3lFClX7hUyJcA+zehdEINnQ8CXWSrVx/IYRjQdo/Y=; b=p2PeTdlPi7ykqFA4k2aMQlViGMSPkUcvRU4eNt2vXsRETKdd6CSsqsf4pu9kTg0OuB YQj5dS9uKhyJfidM2f36hFNHUUDANL5dY59Qs7OpVSBrzhozcNWSsWcy1BHAl8Yv0/uZ MuPx1ADH3Rmi7vt4pA0jp90DTo5wTKDAPDw+VAIfePvDQ5nXFPQYyp3CaF/gcT4VhFkz UY4I3gvvUboDqjykbx77Dz5ueOtkt1j3HHIWjGjpMhVQWSX0SjvvHngb2U3ozlEsHitb GqGzqRtd1qQ7yElS7+TLb86Gmogb/gS0D1S2arTG7c1gpvolGA+ckhGkwqSE3nXNgCVy DFdw== 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:content-transfer-encoding :in-reply-to:user-agent; bh=Pn3lFClX7hUyJcA+zehdEINnQ8CXWSrVx/IYRjQdo/Y=; b=rBdwtHmckzCJF2qLWfouKNnK04pxdaEXqIuz4BeR7Mqvz2u4idpEVwuHV7W1V1int6 MSlbXk27VRiI/Q1dmMCdieLmfXX+ZS7mDRQC8U5SZpG+6elYu/P7IGyExjNX/rQ8VwJt V/fIj0TWO4XQLc2Aqr9LP6bMUfqGlNT8iRCEwAkrw/q8aZdKVcyllH9mWIbgGhhLLlv0 86TVNATXyTvkXQRUWvXFuvVaFvjbAqib1SHe66jpRCZ+D8+KhR/GzBd/kZ9t/wKG9cbL Pssm2ASR3i76ab1sERhmt5P8kL7du5BocT439DLQK/zdr02sQ5hnctPZyk8vGmFbD3YJ 3LqQ== X-Gm-Message-State: AOAM530DeQzMj2qGOhcUsmdVybwQHKvweZhQRmFGhMqbdWLZq752gUh/ Hdz9Q/OMgLoZhP6GQYCuoy1yjw== X-Google-Smtp-Source: ABdhPJxRxeGzhNpe2xf7+WWx9J8gRv5mIcy03RFpB62Xm2JFBPnOvjyUzYFNkxLuDGZpPDM+zpZNOg== X-Received: by 2002:a02:b709:: with SMTP id g9mr6136348jam.90.1609982236299; Wed, 06 Jan 2021 17:17:16 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id b22sm2413629ioa.10.2021.01.06.17.17.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 17:17:15 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 5510880052F; Wed, 6 Jan 2021 19:17:14 -0600 (CST) Date: Wed, 6 Jan 2021 19:17:14 -0600 From: Justin Pryzby To: Tomas Vondra Cc: Josef =?utf-8?B?xaBpbcOhbmVr?= , pgsql-hackers@lists.postgresql.org Subject: Re: [PATCH] Simple progress reporting for COPY command Message-ID: <20210107011714.GU1849@telsasoft.com> References: <6e7b056e-faff-40f6-730d-3ad6d2d1b5e9@enterprisedb.com> <1562ca9b-ffb5-e5e9-0399-33db90dbe153@enterprisedb.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="aM3YZ0Iwxop3KEKx" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1562ca9b-ffb5-e5e9-0399-33db90dbe153@enterprisedb.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --aM3YZ0Iwxop3KEKx Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Wed, Jan 06, 2021 at 10:44:49PM +0100, Tomas Vondra wrote: > On 1/5/21 11:02 AM, Josef Šimánek wrote: > > I'm attaching the whole patch since commitfest failed to ingest the > > last incremental on CI. > > > > Yeah, the whole patch needs to be attached for the commitfest tester to work > correctly - it can't apply pieces from multiple messages, etc. > > Anyway, I pushed this last version of patch, after a couple more tweaks, > mainly to the docs - one place used pg_stat_copy_progress, the section was > not indexed properly, and so on. Some more doc fixes. From 0616f448057905ab9b3218ebddfdd3af52e62bac Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Wed, 6 Jan 2021 19:08:11 -0600 Subject: [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f --- doc/src/sgml/monitoring.sgml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 43fe8ae383..3cdb1aff3c 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, Whenever COPY is running, the pg_stat_progress_copy view will contain one row - for each backend that is currently running COPY command. - The table bellow describes the information that will be reported and provide - information how to interpret it. + for each backend that is currently running a COPY command. + The table below describes the information that will be reported and provides + information about how to interpret it. @@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, - datid text + datid oid OID of the database to which this backend is connected. @@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, OID of the table on which the COPY command is executed. - It is set to 0 if SELECT query is provided. + It is set to 0 if copying from a SELECT query. -- 2.17.0 --aM3YZ0Iwxop3KEKx Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch" From 0616f448057905ab9b3218ebddfdd3af52e62bac Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Wed, 6 Jan 2021 19:08:11 -0600 Subject: [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f --- doc/src/sgml/monitoring.sgml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 43fe8ae383..3cdb1aff3c 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, Whenever COPY is running, the pg_stat_progress_copy view will contain one row - for each backend that is currently running COPY command. - The table bellow describes the information that will be reported and provide - information how to interpret it. + for each backend that is currently running a COPY command. + The table below describes the information that will be reported and provides + information about how to interpret it.
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, - datid text + datid oid OID of the database to which this backend is connected. @@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, OID of the table on which the COPY command is executed. - It is set to 0 if SELECT query is provided. + It is set to 0 if copying from a SELECT query. -- 2.17.0 --aM3YZ0Iwxop3KEKx--