| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: doc: vacuum full, fillfactor, and "extra space" |
| Date: | 2019-12-27 10:58:18 |
| Message-ID: | alpine.DEB.2.21.1912271150160.27864@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Justin,
> I started writing this patch to avoid the possibly-misleading phrase: "with no
> extra space" (since it's expected to typically take ~2x space, or 1x "extra"
> space).
>
> But the original phrase "with no extra space" seems to be wrong anyway, since
> it actually follows fillfactor, so say that. Possibly should be backpatched.
Patch applies and compiles.
Given that the paragraph begins with "Plain VACUUM (without FULL)", it is
better to have the VACUUM FULL explanations on a separate paragraph, and
the fillfactor precision makes it explicit about what it does, although it
could also be material for the NOTES section below.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2019-12-27 11:15:18 | Re: Calling PLpgSQL function with composite type fails with an error: "ERROR: could not open relation with OID ..." |
| Previous Message | Julien Rouhaud | 2019-12-27 09:15:33 | Re: Expose lock group leader pid in pg_stat_activity |