| From: | Alvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at> |
| 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-06 16:39:25 |
| Message-ID: | asUjbcveDkxJA0oG@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"In Europe they call me Niklaus Wirth; in the US they call me Nickel's worth.
That's because in Europe they call me by name, and in the US by value!"
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-Revamp-REPACK-doc-refentry-page.patch | text/x-diff | 21.3 KB |
| sql-repack.html | text/html | 21.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-10-06 16:43:47 | Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers |
| Previous Message | Greg Burd | 2026-10-06 16:29:12 | Re: Let an ordering index scan hand its ORDER BY value to the target list |