| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | chris+postgresql(at)qwirx(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Logical replication subscription owner |
| Date: | 2020-04-22 17:40:29 |
| Message-ID: | 20200422174029.GA17052@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On 2020-Apr-15, PG Doc comments form wrote:
> If the logical replication subscription is owned by a role that is not
> allowed to login (for example, if the LOGIN privilege is removed after the
> subscription is created) then the logical replication worker (which uses the
> owner to connect to the database) will start to fail with this error
> (repeated every 5 seconds), which is pretty much undocumented:
>
> FATAL: role "XXX" is not permitted to log in
> LOG: background worker "logical replication worker" (PID X) exited with
> exit code 1
>
> You might want to include that error message in the docs, to ensure that web
> searches for it bring the user to this documentation.
I wonder if a better answer is to allow the connection when the
REPLICATION priv is granted, ignoring the LOGIN prov.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-04-22 17:46:11 | Re: Logical replication subscription owner |
| Previous Message | PG Doc comments form | 2020-04-22 15:29:36 | Add that changing the `argname` will raise exception in procedure/function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-04-22 17:46:11 | Re: Logical replication subscription owner |
| Previous Message | Alvaro Herrera | 2020-04-22 17:18:06 | Re: More efficient RI checks - take 2 |