pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Josef Šimánek <josef.simanek@gmail.com>
Cc: pgsql-hackers@postgresql.org, Tomas Vondra <tomas.vondra@enterprisedb.com>
Subject: Re: Improvements and additions to COPY progress reporting
Date: Fri, 12 Feb 2021 18:37:32 -0600
Message-ID: <20210213003732.GJ1793@telsasoft.com> (raw)
In-Reply-To: <CAEze2WhbvkoSm6zs7Jaupe+Ln0ttP6m1Fb3WLodo8-SdTxq6WQ@mail.gmail.com>
References: <CALj2ACW-nY0TAQRzUyKmomwD0udobb53iopFDTn2NytwcSR07w@mail.gmail.com>
	<CAEze2Wh753JM+W25grkM30GUXvE_bjHVEJdkdvhnL8SthNSJVA@mail.gmail.com>
	<CALj2ACUCASUO9Le2Lq6d_gEdHtVEH6EFG19R-kKTWtRf2TmnVw@mail.gmail.com>
	<CAEze2Wi2BS12wj3ZggQwcacW8e9inruaSZpfbWZ40O3Xp_Q-aA@mail.gmail.com>
	<CAFp7QwqKwZikq6fdOC7+EShw+ozWzNo63e4PFatcFvAGH4qaag@mail.gmail.com>
	<CALj2ACWTEPRJY72NWuwj9eL3=pfx=KVXq4srpe-EwNPO7GKvBA@mail.gmail.com>
	<CAEze2WiTSjepqc-JO29yaydeXdgXeqxJ1Hi-DAMvfzKqnnje2w@mail.gmail.com>
	<CAEze2Wh_ohsJuRQ7kkCnfZWNqHXLsJCFsKzRauoGNeNgG=eosg@mail.gmail.com>
	<CALj2ACWNo1jSQDnGTx+v9jR27BOen59sWdp+j+JrWwuFuhB8Rg@mail.gmail.com>
	<CAEze2WhbvkoSm6zs7Jaupe+Ln0ttP6m1Fb3WLodo8-SdTxq6WQ@mail.gmail.com>

inline patch 1: doc/src/sgml/ref/analyze.sgml (+6/-0 lines) download inline-1.patch--- a/doc/src/sgml/ref/analyze.sgml +++ b/doc/src/sgml/ref/analyze.sgml @@ -273,6 +273,12 @@ ANALYZE [ VERBOSE ] [ <replaceable class="parameter">table_and_columns</replacea will not record new statistics for that table. Any existing statistics will be retained. </para> + + <para> + Each backend running the <command>ANALYZE</command> command will report their + progress to the <structname>pg_stat_progress_analyze</structname> view. + See <xref linkend="analyze-progress-reporting"/> for details. + </para>
I think this should say: "..will report its progress to.." Or: "The progress of each backend running >ANALYZE< is reported in the >pg_stat_progress_analyze< view." -- Justin

view thread (51+ messages)  latest in thread

Message-ID: <20210213003732.GJ1793@telsasoft.com>
Permalink:  ../20210213003732.GJ1793@telsasoft.com/
Also on:    postgresql.org/message-id/20210213003732.GJ1793@telsasoft.com

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, boekewurm+postgres@gmail.com, bharath.rupireddyforpostgres@gmail.com, josef.simanek@gmail.com, tomas.vondra@enterprisedb.com
  Subject: Re: Improvements and additions to COPY progress reporting
  In-Reply-To: <20210213003732.GJ1793@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox