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

From Antonin Houska
Subject Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes
Date
Msg-id 93720.1791314958@localhost
Whole thread
In response to Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes  (Alvaro Herrera <alvherre@kurilemu.de>)
Responses Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes
List pgsql-hackers
Alvaro Herrera <alvherre@kurilemu.de> wrote:

> Actually, after going over Thom Brown's report on MVCC unsafety, I
> looked again and decided to move the <warning> box and the list of
> restrictions for CONCURRENTLY to also appear in the "Notes on Concurrent
> Operation" subsection, instead of inside the "Parameters" section.
> So here it is again, both in patch form as well as HTML.

[ Thanks for the HTML. ]

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

No objections regarding the "Notes on Concurrent Operation" section.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Next
From: Nathan Bossart
Date:
Subject: Re: use a non-locking initial test in TAS_SPIN on AArch64