| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: doc: vacuum full, fillfactor, and "extra space" |
| Date: | 2020-03-28 10:23:11 |
| Message-ID: | CAA4eK1L90pXY8GO2m1GFW=27RPyuqyk0LeuAdRuo_UUV-BWUsw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 29, 2020 at 9:10 PM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 2020-01-20 06:30, Justin Pryzby wrote:
>
> 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.
>
Justin, would you like to address this comment of Peter E.?
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-03-28 10:44:04 | Re: WAL usage calculation patch |
| Previous Message | Amit Kapila | 2020-03-28 09:59:34 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |