| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Don't truncate heap when VACUUM's failsafe is in effect. |
| Date: | 2021-04-13 19:58:58 |
| Message-ID: | E1lWPBa-0001my-2Z@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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(dot)mshk(at)gmail(dot)com>
Discussion: https://postgr.es/m/CAD21AoDWRh6oTN5T8wa+cpZUVpHXET8BJ8Da7WHVHpwkPP6KLg@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/60f1f09ff44308667ef6c72fbafd68235e55ae27
Modified Files
--------------
src/backend/access/heap/vacuumlazy.c | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2021-04-13 22:53:59 | pgsql: Initialize t_self and t_tableOid in statext_expressions_load |
| Previous Message | Tom Lane | 2021-04-13 19:39:49 | pgsql: Allow table-qualified variable names in ON CONFLICT ... WHERE. |