At Fri, 10 Sep 2021 16:55:48 +0900, Abhishek Bhola
wrote in
> So is there any solution to this issue?
> I did try to increase the wal_sender_timeout and it broke the pub/sub.
> I increased the wal_receiver_timeout and it wouldn't attempt to restart the
> subscription until that time elapsed.
> D
So is there any solution to this issue?
I did try to increase the wal_sender_timeout and it broke the pub/sub.
I increased the wal_receiver_timeout and it wouldn't attempt to restart the
subscription until that time elapsed.
Due to that, the WAL segments got removed by the time it came up again and
At Thu, 9 Sep 2021 16:06:25 +0900, Abhishek Bhola
wrote in
> sourcedb:~$ postgres --version
> postgres (PostgreSQL) 11.6
>
> Sorry for missing this information.
> But looks like this fix is already included in the version I am running.
Ok. I'm not sure but there may be a case where too-busy (o
sourcedb:~$ postgres --version
postgres (PostgreSQL) 11.6
Sorry for missing this information.
But looks like this fix is already included in the version I am running.
Regards,
Abhishek Bhola
On Thu, Sep 9, 2021 at 3:56 PM Kyotaro Horiguchi
wrote:
> At Thu, 9 Sep 2021 14:52:25 +0900, Abhishek B
At Thu, 9 Sep 2021 14:52:25 +0900, Abhishek Bhola
wrote in
> I have found some questions about the same error, but didn't find any of
> them answering my problem.
>
> The setup is that I have two Postgres11 clusters (A and B) and they are
> making use of publication and subscription features to
I have found some questions about the same error, but didn't find any of
them answering my problem.
The setup is that I have two Postgres11 clusters (A and B) and they are
making use of publication and subscription features to copy data from A to
B.
A (source DB- publication) --> B (t
