From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | 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:46:11 |
Message-ID: | 20200422174611.GX13712@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
Greetings,
* Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> 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.
Erm, no, I wouldn't have thought that'd make sense- maybe someone
specifically wants to stop allowing that role to login and they remove
LOGIN? That REPLICATION would override that would surely be surprising
and counter-intuitive..
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2020-04-22 20:23:31 | Re: terminology in example |
Previous Message | Alvaro Herrera | 2020-04-22 17:40:29 | Re: Logical replication subscription owner |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2020-04-22 17:46:22 | Re: More efficient RI checks - take 2 |
Previous Message | Alvaro Herrera | 2020-04-22 17:40:29 | Re: Logical replication subscription owner |