Timeline for How to predict how much space a VACUUM FULL would reclaim?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2020 at 15:59 | comment | added | Laurenz Albe |
No, because I included dead_tuple_len. The free space is approx_free_space.
|
|
| Nov 5, 2020 at 15:45 | comment | added | OrangeDog |
Can I confirm that this also means there can be around reclaimable bytes of new updates added without increasing the disk usage (assuming there has been a non-full vacuum)? Or is it likely to be a lot less than that?
|
|
| Nov 5, 2020 at 12:03 | history | edited | Colin 't Hart | CC BY-SA 4.0 |
Fix typo. Include detail from comment.
|
| Nov 5, 2020 at 12:00 | comment | added | OrangeDog | @Colin'tHart I think my client is more strict than necessary about quoting keywords. | |
| Nov 5, 2020 at 11:48 | comment | added | Colin 't Hart |
@OrangeDog Worked for me without quoting table (now called table_name in the current edit).
|
|
| Nov 5, 2020 at 11:43 | history | edited | Laurenz Albe | CC BY-SA 4.0 |
added 5 characters in body
|
| Nov 5, 2020 at 11:33 | vote | accept | OrangeDog | ||
| Nov 5, 2020 at 11:04 | history | answered | Laurenz Albe | CC BY-SA 4.0 |