On Mon, Nov 28, 2016 at 8:11 AM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > When a new participant arrives here, if it finds that we're still in > the INIT phase, then it enters an election to see if it can build the > bitmap; one lucky participant wins and does that, while any other > participants twiddle their thumbs at the next BarrierWait call. If a > new participant finds that we're already in the BUILDING phase when it > arrives, then it has missed that election and just has to wait for the > building to be completed. Once they all agree that building has > finished, we move onto scanning. If a new arrival finds that we're in > SCANNING phase, then it happily scans and emits tuples. Does that > make sense? > > Not sure exactly how to coordinate rescans yet, but probably with > BarrierWaitSet(&something->barrier, PBS_PHASE_INIT). >
Do you think that using barrier's will simplify the patch as compared to using condition variables because in that case, it will make sense to use barriers? -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers