On 17/06/2026 21:19, Alvaro Herrera wrote:
> 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].
>
>> [1]:
https://www.postgresql.org/message-id/flat/CADzfLwXbUWuS6H4uJEFVL1jS1kzsVnuJ%2BzX1%2BtAEhQxBnEiGKw%40mail.gmail.com
>
> 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.
There's still an open item for this on the wiki [1]. Is the decision to
let this slip for pg19? If so, please update the open items list. Thanks!
[1] https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items
- Heikki
