Re: why there is not VACUUM FULL CONCURRENTLY? - Mailing list pgsql-hackers

From jian he
Subject Re: why there is not VACUUM FULL CONCURRENTLY?
Date
Msg-id CACJufxGE4vDVBd_KDFsTnXoMPKobx-Qqk=f8boZYKJNvUVb3AQ@mail.gmail.com
Whole thread Raw
In response to Re: why there is not VACUUM FULL CONCURRENTLY?  (jian he <jian.universality@gmail.com>)
Responses Re: why there is not VACUUM FULL CONCURRENTLY?
List pgsql-hackers
hi.
some more minor comments about v13-0001.

GetCommandLogLevel also needs to specify LogStmtLevel for T_RepackStmt?

/*
 * (CLUSTER might change the order of
 * rows on disk, which could affect the ordering of pg_dump
 * output, but that's not semantically significant.)
*/
do we need adjust this comment in ClassifyUtilityCommandAsReadOnly
for the REPACK statement?


  <para>
   <productname>PostgreSQL</productname> has the ability to report the
progress of
   certain commands during command execution.  Currently, the only commands
   which support progress reporting are <command>ANALYZE</command>,
   <command>CLUSTER</command>,
   <command>CREATE INDEX</command>, <command>VACUUM</command>,
   <command>COPY</command>,
   and <xref linkend="protocol-replication-base-backup"/> (i.e., replication
   command that <xref linkend="app-pgbasebackup"/> issues to take
   a base backup).
   This may be expanded in the future.
  </para>
also need to mention <command>REPACK</command>?


"The CLUSTER command is deprecated",
then do we need to say something
in doc/src/sgml/ref/clusterdb.sgml?



pgsql-hackers by date:

Previous
From: Rintaro Ikeda
Date:
Subject: Re: Suggestion to add --continue-client-on-abort option to pgbench
Next
From: Andres Freund
Date:
Subject: Re: Non-reproducible AIO failure