public inbox for [email protected]
help / color / mirror / Atom feedFrom: Hayato Kuroda (Fujitsu) <[email protected]>
To: 'vignesh C' <[email protected]>
To: Noah Misch <[email protected]>
Cc: [email protected] <[email protected]>
Cc: [email protected] <[email protected]>
Subject: RE: sequencesync worker race with REFRESH SEQUENCES
Date: Fri, 10 Jul 2026 08:18:15 +0000
Message-ID: <OS9PR01MB121493C3AF11F71F4CF5DA4EDF5FD2@OS9PR01MB12149.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CALDaNm2GBdszCTSJyiWrG244zzhwaNftqfXNT5YsCQsxJR22Dg@mail.gmail.com>
References: <[email protected]>
<CALDaNm2GBdszCTSJyiWrG244zzhwaNftqfXNT5YsCQsxJR22Dg@mail.gmail.com>
Dear Vignesh, Noah,
Agree the basic approach that we avoid the re-initializing the catalog.
My primitive idea is to follow what slotsync does. SlotSyncCtxStruct::syncing is
checked from the SQL function and the slotsync worker, and either of them can
continue. So we may be able to have LogicalRepCtxStruct::synching_seqs or
something to indicate the status.
But there might be other ways, needs to be investigated.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
view thread (9+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: RE: sequencesync worker race with REFRESH SEQUENCES
In-Reply-To: <OS9PR01MB121493C3AF11F71F4CF5DA4EDF5FD2@OS9PR01MB12149.jpnprd01.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox