Re: vacuum freeze - possible improvements

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Virender Singla <virender(dot)cse(at)gmail(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: vacuum freeze - possible improvements
Date: 2021-04-13 11:05:26
Message-ID: CAApHDvq-qYAA6Z69q7KyLJizWNfnJN+k=wKxmGXM5cKeDndw+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 13 Apr 2021 at 19:48, Virender Singla <virender(dot)cse(at)gmail(dot)com> wrote:
> Yes another thing here is anti wraparound vacuum also cleans dead tuples but i am not sure what we can do to avoid that.
> There can be vacuum to only freeze the tulpes?

You might want to have a look at [1], which was just pushed for PG14.

In particular:

> When the failsafe triggers, VACUUM takes extraordinary measures to
> finish as quickly as possible so that relfrozenxid and/or relminmxid can
> be advanced. VACUUM will stop applying any cost-based delay that may be
> in effect. VACUUM will also bypass any further index vacuuming and heap
> vacuuming -- it only completes whatever remaining pruning and freezing
> is required. Bypassing index/heap vacuuming is enabled by commit
> 8523492d, which made it possible to dynamically trigger the mechanism
> already used within VACUUM when it is run with INDEX_CLEANUP off.

David

[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=1e55e7d1755cefbb44982fbacc7da461fa8684e6

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-04-13 11:58:33 Re: Old Postgresql version on i7-1165g7
Previous Message Yura Sokolov 2021-04-13 10:20:34 Re: Old Postgresql version on i7-1165g7