Hi, On Tue, Oct 20, 2026 at 2:21 PM Hayato Kuroda (Fujitsu) <[email protected]> wrote: > > I agree that we cannot catch all possible errors. After thinking about this > > more, there are other errors—such as deadlock timeout or lock timeout—that > > cannot easily be pre-checked, so adding an error context looks like a good > > approach to me. Attached is a patch that adds the error context as > > suggested. > > Thanks for the patch. I initially felt that setting/reseting the error context > can be in the copy_sequence(), but yours seem to slightly better. > get_and_validate_seq_info() may report another error. > > One comment for the test: below lines may not be needed, because REFRESH > SEQUENCES > does not require apply workers, and the launcher eventually starts workers > with > the appropriate owner. Doesn't upcoming wait_for_log() enough?
Agreed. Here is the new version that removes this. Best Regards, Zhijie Hou
v3-0001-Add-error-context-for-sequence-synchronization.patch
Description: Binary data
