From: | Ian Barwick <ian(at)2ndquadrant(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-docs(at)postgresql(dot)org |
Subject: | Description tweak for vacuumdb |
Date: | 2016-01-04 02:05:40 |
Message-ID: | 5689D374.7080703@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
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
Attachment | Content-Type | Size |
---|---|---|
doc-vacuumdb-94.patch | text/x-patch | 876 bytes |
doc-vacuumdb-head.patch | text/x-patch | 934 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Jürgen Purtz | 2016-01-04 15:35:36 | Graphic to visualize data flow between processes, buffers and files |
Previous Message | Tom Lane | 2015-12-27 17:58:30 | Re: PLs and pseudo-types |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2016-01-04 02:09:02 | Re: Broken lock management in policy.c. |
Previous Message | Peter Geoghegan | 2016-01-04 02:04:41 | Re: Broken lock management in policy.c. |