| From: | Darafei Praliaskouski <me(at)komzpa(dot)net> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Takayuki Tsunakawa <maumau307(at)gmail(dot)com> |
| Subject: | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |
| Date: | 2019-04-06 07:53:07 |
| Message-ID: | 155453718772.16480.8982498117656778884.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The following review has been posted through the commitfest application:
make installcheck-world: not tested
Implements feature: not tested
Spec compliant: not tested
Documentation: not tested
I have read disable-vacuum-truncation_v6.patch.
I like it the way it is.
Word "truncation" for me means "remove everything from the table" (as in TRUNCATE) and I don't want VACUUM to do that :), shrink feels appropriate.
TRIM has a connotation from SSD drives, where you can discard blocks in the middle of your data and let the underlying infrastructure handle space allocation on it.
Please keep it for the good times Postgres can punch a hole in the middle of relation and let filesystem handle that space.
The new status of this patch is: Ready for Committer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darafei Komяpa Praliaskouski | 2019-04-06 07:56:16 | Re: Berserk Autovacuum (let's save next Mandrill) |
| Previous Message | GUO Rui | 2019-04-06 07:26:52 | Re: Google Summer of Code: question about GiST API advancement project |