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

From Álvaro Herrera
Subject Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes
Date
Msg-id asPANhU1DRUwSZT0@alvherre.pgsql
Whole thread
In response to Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes  (shihao zhong <zhong950419@gmail.com>)
Responses Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes
List pgsql-hackers
On 2026-Sep-27, shihao zhong wrote:

> 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.

Yeah, that sounds appropriate.

I think the original <note> paragraph is worth rewriting more deeply
though rather than just adding one more paragraph; I think some of the
things it mentions are not so relevant from the user's POV, and also I
think we can use some small changes elsewhere in the page.

What do you think of the attached?  I used -U7 in `git format-patch` so
that the surrounding can be read directly from the patch.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/

Attachment

pgsql-hackers by date:

Previous
From: Rui Zhao
Date:
Subject: Re: Serverside SNI support in libpq
Next
From: Hannu Krosing
Date:
Subject: Re: Direct TOAST v2, faster, smaller and no migration needed