Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout
Date: 2026-09-18 00:29:56
Message-ID: CAGRkXqTXJiEXgO4NjOyDQoFHNnEef8+S82zgjSL1yx_1N+Ffwg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Alvaro,

> Thanks. I pushed the patch, but didn't keep the detailed comment.

Thanks for pushing it, and for the backpatch to 19.

> Did you mean to reference the proposed new test in this paragraph?

Yes, sorry, that paragraph was about the test in 0002. You are right
that it is timing sensitive. It only caught the bug after I added a
pg_sleep before the COMMIT, so it would be fragile on slow machine.
Leaving it out is fine.

Thanks,
Shihao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-09-18 00:42:23 Re: Add a hook for handling logical decoding messages on subscribers.
Previous Message Tomas Vondra 2026-09-18 00:20:15 Re: issues with eager aggregation