Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Antonin Houska <ah(at)cybertec(dot)at>, Radim Marek <radim(at)boringsql(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes
Date: 2026-10-05 15:24:41
Message-ID: asPANhU1DRUwSZT0@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
v3-0001-doc-Document-REPACK-limits-and-point-to-VACUUM-fo.patch text/x-diff 7.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2026-10-05 15:37:09 Re: Direct TOAST v2, faster, smaller and no migration needed
Previous Message Rui Zhao 2026-10-05 15:15:29 Re: Serverside SNI support in libpq