pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ian Barwick <ian@2ndquadrant.com>
To: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
To: pgsql-docs@postgresql.org
Subject: Description tweak for vacuumdb
Date: Mon, 4 Jan 2016 11:05:40 +0900
Message-ID: <5689D374.7080703@2ndquadrant.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>

Hi

Like the docs say, vacuumdb is a "wrapper around the SQL command VACUUM"
which I used to use in dim-and-distant pre-autovacuum days came for cronjobs,
but until messing around with pg_upgrade recently I hadn't really had much
use for it. Anyway, the docs also say "There is no effective difference
between vacuuming and analyzing databases via this utility and via other
methods for accessing the server", which IMHO seems a bit out-of-date as
it now does two things which you can't do directly via e.g. psql:

- generate statistics in stages (9.4)
- parallel vacuum (9.5)

Attached patches (for 9.4 and 9.5/HEAD) update the description to make
clear that it now does a bit more than just execute a single command.


Regards

Ian Barwick


-- 
 Ian Barwick                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Attachments:

doc-vacuumdb-94.patch (text/x-patch, 875B) download diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml new file mode 100644 index 3ecd999..35e3d6f *** a/doc/src/sgml/ref/vacuumdb.sgml --- b/doc/src/sgml/ref/vacuumdb.sgml *************** PostgreSQL documentation *** 65,71 **** command <xref linkend="SQL-VACUUM">. There is no effective difference between vacuuming and analyzing databases via this utility and via other methods for accessing the ! server. </para> </refsect1> --- 65,73 ---- command <xref linkend="SQL-VACUUM">. There is no effective difference between vacuuming and analyzing databases via this utility and via other methods for accessing the ! server. However it does provide additional functionality for generating ! statistics in stages, which is useful when optimizing a newly populated ! database. </para> </refsect1>
doc-vacuumdb-head.patch (text/x-patch, 933B) download diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml new file mode 100644 index 92b8984..d640887 *** a/doc/src/sgml/ref/vacuumdb.sgml --- b/doc/src/sgml/ref/vacuumdb.sgml *************** PostgreSQL documentation *** 65,71 **** command <xref linkend="SQL-VACUUM">. There is no effective difference between vacuuming and analyzing databases via this utility and via other methods for accessing the ! server. </para> </refsect1> --- 65,73 ---- command <xref linkend="SQL-VACUUM">. There is no effective difference between vacuuming and analyzing databases via this utility and via other methods for accessing the ! server. However it does provide additional functionality for generating ! statistics in stages, which is useful when optimizing a newly populated ! database, and for executing vacuum or analyze commands in parallel. </para> </refsect1>

view thread (2+ messages)  latest in thread

Message-ID: <5689D374.7080703@2ndquadrant.com>
Permalink:  ../5689D374.7080703@2ndquadrant.com/
Also on:    postgresql.org/message-id/5689D374.7080703@2ndquadrant.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: ian@2ndquadrant.com, pgsql-docs@postgresql.org
  Subject: Re: Description tweak for vacuumdb
  In-Reply-To: <5689D374.7080703@2ndquadrant.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