| commit | 60f1f09ff44308667ef6c72fbafd68235e55ae27 | |
| author | Peter Geoghegan <pg@bowt.ie> | |
| Tue, 13 Apr 2021 19:58:31 +0000 (13 12:58 -0700) | ||
| committer | Peter Geoghegan <pg@bowt.ie> | |
| Tue, 13 Apr 2021 19:58:31 +0000 (13 12:58 -0700) | ||
| tree | b292538abf7696415e2df9aed2019d5777f70285 | treesnapshot (tar.gz zip) |
| parent | 6c0373ab77359c94b279c4e67c91aa623841af65 | commitdiff |
Don't truncate heap when VACUUM's failsafe is in effect.
It seems like a good idea to bypass heap truncation when the wraparound
failsafe mechanism (which was added in commit 1e55e7d1) is in effect.
Deliberately don't bypass heap truncation in the INDEX_CLEANUP=off case,
even though it is similar to the failsafe case. There is already a
separate reloption (and related VACUUM parameter) for that.
Reported-By: Masahiko Sawada <sawada.mshk@gmail.com>
Discussion: https://postgr.es/m/CAD21AoDWRh6oTN5T8wa+cpZUVpHXET8BJ8Da7WHVHpwkPP6KLg@mail.gmail.com
It seems like a good idea to bypass heap truncation when the wraparound
failsafe mechanism (which was added in commit 1e55e7d1) is in effect.
Deliberately don't bypass heap truncation in the INDEX_CLEANUP=off case,
even though it is similar to the failsafe case. There is already a
separate reloption (and related VACUUM parameter) for that.
Reported-By: Masahiko Sawada <sawada.mshk@gmail.com>
Discussion: https://postgr.es/m/CAD21AoDWRh6oTN5T8wa+cpZUVpHXET8BJ8Da7WHVHpwkPP6KLg@mail.gmail.com
| src/backend/access/heap/vacuumlazy.c | diffblobblamehistory |