On Tue, Apr 5, 2022 at 7:06 PM Ashutosh Bapat <ashutosh.bapat....@gmail.com> wrote: > > On Tue, Apr 5, 2022 at 6:21 AM Peter Smith <smithpb2...@gmail.com> wrote: > > > > Below are some other name ideas. Maybe they are not improvements, but > > it might help other people to come up with something better. > > > > subscribe_publocal_only = true/false > > origin = pub_only/any > > adjacent_data_only = true/false > > direct_subscriptions_only = true/false > > ... > > FWIW, The subscriber wants "changes originated on publisher". From > that angle origin = publisher/any looks attractive. It also leaves > open the possibility that the subscriber may ask changes from a set of > origins or even non-publisher origins. >
So, how are you imagining extending it for multiple origins? I think we can have multiple origins data on a node when there are multiple subscriptions pointing to the different or same node. The origin names are internally generated names but are present in pg_replication_origin. So, are we going to ask the user to check that table and specify it as an option? But, note, that the user may not be able to immediately recognize which origin data is useful for her. Surely, with some help or advice in docs, she may be able to identify it but that doesn't seem so straightforward. The other point is that such an option won't be applicable for initial sync as we can't differentiate between data from a local or remote node. -- With Regards, Amit Kapila.