| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: doc: vacuum full, fillfactor, and "extra space" |
| Date: | 2020-01-29 15:40:34 |
| Message-ID: | 313bd4cc-8ef4-1d75-7cac-c30635298aa0@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-01-20 06:30, Justin Pryzby wrote:
> Rebased against 40d964ec997f64227bc0ff5e058dc4a5770a70a9
I'm not sure that description of parallel vacuum in the middle of
non-full vs. full vacuum is actually that good. I think those sentences
should be moved to a separate paragraph.
About your patch, I don't think this is clearer. The fillfactor stuff
is valid to be mentioned, but the way it's being proposed makes it sound
like the main purpose of VACUUM FULL is to bloat the table to make
fillfactor room. The "no extra space" wording made sense to me, with
the fillfactor business perhaps worth being put into a parenthetical note.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-29 15:45:51 | Re: making the backend's json parser work in frontend code |
| Previous Message | Konstantin Knizhnik | 2020-01-29 15:30:44 | Re: [Proposal] Global temporary tables |