From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | CREATE SUBSCRIPTION documentation |
Date: | 2017-06-19 17:28:07 |
Message-ID: | CAMkU=1xNOxJM1fRcbEfN8hq=UGky_FDx-TKL7fe+ow1BaTRHjg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
https://www.postgresql.org/docs/devel/static/sql-createsubscription.html
Has the note:
See Section 26.2.5.1
<https://www.postgresql.org/docs/devel/static/warm-standby.html#streaming-replication-authentication>
for
details on how to configure access control between the subscription and the
publication instance.
But that section seems to describe authentication for physical, not
logical, replication. Those two no longer use the same access control
methods. For logical replication, the role has to have replication
attribute or be a superuser, but the role does not need to have replication
listed in the pg_hba.conf.
I think it would be better to instead reference:
https://www.postgresql.org/docs/devel/static/logical-replication-security.html
And on that page, it says:
"The role used for the replication connection must have the REPLICATION
attribute"
Should also say something like "or be a superuser". It is bit tedious to
say that everywhere, but the docs are supposed to be a bit tedious.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Shubham Barai | 2017-06-19 17:30:23 | Re: GSoC 2017 weekly progress reports (week 3) |
Previous Message | Alvaro Herrera | 2017-06-19 17:19:53 | Re: GSoC 2017 weekly progress reports (week 3) |