Re: New vacuum option to do only freezing
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, "Bossart,
Nathan" <bossartn@amazon.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>,
Michael Paquier <michael@paquier.xyz>
Date: 2019-05-01T16:39:13Z
Lists: pgsql-hackers
On Wed, May 1, 2019 at 12:14 PM Andres Freund <andres@anarazel.de> wrote: > On 2019-04-06 16:13:53 +0900, Michael Paquier wrote: > > On Sat, Apr 06, 2019 at 11:31:31AM +0900, Masahiko Sawada wrote: > > > Yes, but Fujii-san pointed out that this option doesn't support toast > > > tables and I think there is not specific reason why not supporting > > > them. So it might be good to add toast.vacuum_index_cleanup. Attached > > > patch. > > > > Being able to control that option at toast level sounds sensible. I > > have added an open item about that. > > Robert, what is your stance on this open item? It's been an open item > for about three weeks, without any progress. The actual bug in this patch needs to be fixed, but I see we have another open item for that. This open item, as I understand it, is all about whether we should add another reloption so that you can control this behavior separately for TOAST tables. In my opinion, that's not a critical change and the open item should be dropped, but others might see it differently. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Add toast-level reloption for vacuum_index_cleanup
- ce59b75d449d 12.0 landed
-
heap_prepare_freeze_tuple: Simplify coding
- 2bf372a4ae26 12.0 landed
-
Fix missing word.
- 6665305e17ed 12.0 landed
-
Allow VACUUM to be run with index cleanup disabled.
- a96c41feec6b 12.0 landed
-
Don't mark pages all-visible spuriously
- d2599ecfcc74 11.0 cited