Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout - Mailing list pgsql-hackers

From shihao zhong
Subject Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout
Date
Msg-id CAGRkXqTXJiEXgO4NjOyDQoFHNnEef8+S82zgjSL1yx_1N+Ffwg@mail.gmail.com
Whole thread
In response to Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout
List 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

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: issues with eager aggregation
Next
From: Masahiko Sawada
Date:
Subject: Re: Add a hook for handling logical decoding messages on subscribers.