| From: | "kato-sho(at)fujitsu(dot)com" <kato-sho(at)fujitsu(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Synchronizing slots from primary to standby |
| Date: | 2022-02-21 07:41:58 |
| Message-ID: | TYCPR01MB684949EA7AA904EE938548C79F3A9@TYCPR01MB6849.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
This patch status is already returned with feedback.
However, I've applied this patch on 27b77ecf9f and tested so report it.
make installcheck-world is passed.
However, when I promote the standby server and update on the new primary server,
apply worker could not start logical replication and emmit the following error.
LOG: background worker "logical replication worker" (PID 14506) exited with exit code 1
LOG: logical replication apply worker for subscription "sub1" has started
ERROR: terminating logical replication worker due to timeout
LOG: background worker "logical replication worker" (PID 14535) exited with exit code 1
LOG: logical replication apply worker for subscription "sub1" has started
It seems that apply worker does not start because wal sender is already exist on the new primary.
Do you have any thoughts about what the cause might be?
test script is attached.
regards, sho kato
| Attachment | Content-Type | Size |
|---|---|---|
| failover.sh | application/octet-stream | 1.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2022-02-21 07:46:07 | Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? |
| Previous Message | Michael Paquier | 2022-02-21 07:41:17 | Re: make tuplestore helper function |