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

From: Antonin Houska <ah(at)cybertec(dot)at>
To: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: shihao zhong <zhong950419(at)gmail(dot)com>, 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-07 07:34:58
Message-ID: 6605.1791358498@localhost
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:

> On 2026-Oct-06, Antonin Houska wrote:
>
> > I suspect there's a thinko in the "Notes on Resources" section. Shouldn't the
> > first paragraph start like this?
> >
> > "When the USING INDEX clause is given and an index scan is chosen, ..."
>
> Hmm, no -- this paragraph tries to explain what happens when we use the
> unsorted option, _or_ we use the sorted option but we use a indexscan to
> implement it. So either the VACUUM FULL, or the indexscan based
> CLUSTER. In this case we only have one extra copy of the table.

ok. What I find disturbing in the first sentence is the "but" conjunction:

"... that clause is given but an index scan is chosen ..."

Shouldn't it rater be "and"?

When I read "but", I usually expect a contradiction. However I see no
contradiction between specifying the USING INDEX clause and choosing index
scan.

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-10-07 07:43:46 Re: [PATCH] psql: avoid CREATE command completion after GRANT/REVOKE CREATE
Previous Message vignesh C 2026-10-07 06:47:26 Re: Parallel Apply