On Tue, Apr 16, 2024 at 12:03 PM Bertrand Drouvot <bertranddrouvot...@gmail.com> wrote: > > On Tue, Apr 16, 2024 at 08:21:04AM +0530, Amit Kapila wrote: > > > There is no clear use case for allowing them in parallel and I feel it > > would add more confusion when it can work sometimes but not other > > times. However, if we receive some report from the field where there > > is a real demand for such a thing, it should be easy to achieve. For > > example, I can imagine that we can have sync_state that has values > > 'started', 'in_progress' , and 'finished'. This should allow us to > > achieve what the current proposed patch is doing along with allowing > > the API to work in parallel when the sync_state is not 'in_progress'. > > > > I think for now let's restrict their usage in parallel and make the > > promotion behavior consistent both for worker and API. > > Okay, let's do it that way. Is it worth to add a few words in the doc related > to > pg_sync_replication_slots() though? (to mention it can not be used if the sync > slot worker is running). >
Yes, this makes sense to me. -- With Regards, Amit Kapila.
