Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes - Mailing list pgsql-hackers

From shihao zhong
Subject Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes
Date
Msg-id CAGRkXqTg-wioCAEWchmieGR3xw5=X4-EgKoDYfT-Cv54dzye1g@mail.gmail.com
Whole thread
In response to Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes  (Antonin Houska <ah@cybertec.at>)
List pgsql-hackers
Hi Antonin,

> I think that the most important thing for the user to know is that the purpose
> of REPACK is to improve performance (via bloat removal and/or clustering),
> whereas "failsafe VACUUM" (i.e. VACUUM with INDEX_CLEANUP set to off) should
> be used to avoid the risk of XID wraparound.
>
> I don't have a good idea about the wording right now.

Here is a try with Fable, as v2 of Radim's patch.

It adds a paragraph to Notes. REPACK is for bloat and clustering. For
wraparound uses VACUUM, because REPACK takes much longer and can fail
late.

Thanks,
Shihao
Attachment

pgsql-hackers by date:

Previous
From: shihao zhong
Date:
Subject: Re: Reset waitStart when a lock wait fails
Next
From: shihao zhong
Date:
Subject: Re: [PATCH] Planner support function for generate_subscripts()