aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_utilcmd.c
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2021-03-03 11:49:12 +0530
committerAmit Kapila <akapila@postgresql.org>2021-03-03 11:59:36 +0530
commit90c737669fd2ab8e02ef7e8200adbce6fccf5c65 (patch)
tree471b9ca3603b2b127afd0560c5ea1fe776318444 /src/backend/parser/parse_utilcmd.c
parent926139dd04bb77ad3c18c9c69544104d15f69672 (diff)
downloadpostgresql-90c737669fd2ab8e02ef7e8200adbce6fccf5c65.tar.gz
postgresql-90c737669fd2ab8e02ef7e8200adbce6fccf5c65.zip
Clarify the usage of max_replication_slots on the subscriber side.
It was not clear in the docs that the max_replication_slots is also used to track replication origins on the subscriber side. Author: Paul Martinez Reviewed-by: Amit Kapila Backpatch-through: 10 where logical replication was introduced Discussion: https://postgr.es/m/CACqFVBZgwCN_pHnW6dMNCrOS7tiHCw6Retf_=U2Vvj3aUSeATw@mail.gmail.com
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions