From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | chris+postgresql(at)qwirx(dot)com |
Subject: | Logical replication subscription owner |
Date: | 2020-04-15 14:02:18 |
Message-ID: | 158695933852.25700.8124720971187835491@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 베이SQL : Postg토토 베이SQL 메일 링리스트 : 2020-04-15 이후 PGSQL-DOCS 14:02 pgsql-hackers |
The following documentation comment has been logged on the website:
Page: /docs/10/sql-altersubscription.html
Description:
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.
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2020-04-15 23:21:15 | Replication: Different naming policy |
Previous Message | Marc Rechté | 2020-04-15 11:12:53 | Backend Flowchart / Developer doc |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2020-04-15 14:12:14 | Re: Parallel copy |
Previous Message | James Coleman | 2020-04-15 13:31:58 | Re: [DOC] Document concurrent index builds waiting on each other |