On Sat, Feb 27, 2021 at 2:35 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > > On Sat, Feb 27, 2021 at 2:47 AM Paul Martinez <paul...@google.com> wrote: > > > > On Fri, Feb 26, 2021 at 5:22 AM Amit Kapila <amit.kapil...@gmail.com> wrote: > > > > > > https://www.postgresql.org/docs/devel/logical-replication-config.html > > > > > > > Ah, yep. I added a clause to the end of the sentence to clarify why we're > > using max_replication_slots here: > > > > - The subscriber also requires the max_replication_slots to be set. > > > > + The subscriber also requires that max_replication_slots be set to > > + configure how many replication origins can be tracked. > > > > LGTM. >
The rebased version attached. As mentioned earlier, I think we can backpatch this patch as this clarifies the already existing behavior. Do let me know if you or others think otherwise? -- With Regards, Amit Kapila.
max_replication_slots_subscriber_doc_v02.patch
Description: Binary data
