Re: Logical replication stops updating - Mailing list pgsql-admin

From Yambu
Subject Re: Logical replication stops updating
Date
Msg-id CALhHtcD_EUgmH-AK-qeYTZkiBoepN+qCtUpCtwAw6new=dbL3Q@mail.gmail.com
Whole thread Raw
In response to Re: Logical replication stops updating  (Yambu <hyambu@gmail.com>)
Responses Re: Logical replication stops updating  (Yambu <hyambu@gmail.com>)
List pgsql-admin
Now i get no errors after increasing wal_receiver_ timeout  and   wal_sender_timeout to 300s on master and slave.

But the slave tables are not getting updates, do i need to do anything since they were so far behind?

On Mon, Dec 21, 2020 at 1:13 PM Yambu <hyambu@gmail.com> wrote:
Hello

I see this error 

 ERROR:  could not start WAL streaming: ERROR:  replication slot "slot1" is active for PID 28212
2020-12-21 11:01:25.630 GMT [1894324] LOG:  background worker "logical replication worker" (PID 1894333) exited with exit code 1

On Mon, Dec 21, 2020 at 12:09 PM Yambu <hyambu@gmail.com> wrote:
Thanks Laurenz,

I got the error below, and i added the primary key on slave table1, but how do i fix the other error  " published relation does not have REPLICA IDENTITY FULL"

logical replication target relation "public.table1" has neither REPLICA IDENTITY index nor PRIMARY KEY and published relation does not have REPLICA IDENTITY FULL

On Mon, Dec 21, 2020 at 11:51 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Mon, 2020-12-21 at 11:48 +0200, Yambu wrote:
> My logical replication stopped updating, how do i make it start again?

Read the standby log file and fix the problem you see there.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

pgsql-admin by date:

Previous
From: Yambu
Date:
Subject: Re: Logical replication stops updating
Next
From: Yambu
Date:
Subject: Re: Logical replication stops updating