| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>, Andres Freund <andres(at)anarazel(dot)de>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Treat <rob(at)xzilla(dot)net> |
| Subject: | Re: Adding REPACK [concurrently] |
| Date: | 2026-06-17 18:19:20 |
| Message-ID: | ajLfxNPl1zg5H--m@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Mihail,
On 2026-Jun-03, Mihail Nikalayeu wrote:
> Hello, everyone!
>
> I think it is a good time to remind we still have a potential deadlock
> issue leading to loosing vast amount of REPACK work.
>
> Best soltuion I was able to craft so far is [1].
Right. I spent some time looking at this patch just before pgconf.dev,
and I have to admit I was a bit scared -- that code is really
non-obvious, and breakage here could mean big trouble in case something
goes wrong in weird situations.
So I think we should let this slip for pg19, and get this patch reviewed
and pushed early in pg20 in the coming weeks, so that we have more of a
chance to discover breakage in the time until pg20 release next year.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Por suerte hoy explotó el califont porque si no me habría muerto
de aburrido" (Papelucho)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-06-17 18:30:13 | Re: mxid_score can become Infinity in pg_stat_autovacuum_scores |
| Previous Message | Heikki Linnakangas | 2026-06-17 18:12:42 | Re: DataChecksumsStateStruct cost_delay fields and locking |