Re: Logical replication timeout problem

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>

To: Fabrice Chapuis <fabrice636861@gmail.com>

Cc: Tang, Haiying/唐海英 <tanghy.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2022-01-14T12:02:57Z

Lists: pgsql-hackers

On Fri, Jan 14, 2022 at 3:47 PM Fabrice Chapuis <fabrice636861@gmail.com> wrote:
>
> If I can follow you, I have to make the following changes:
>

No, not like that but we can try that way as well to see if that helps
to avoid your problem. Am, I understanding correctly even after
modification, you are seeing the problem. Can you try by calling
WalSndKeepaliveIfNecessary() instead of WalSndKeepalive()?

-- 
With Regards,
Amit Kapila.

Commits

Fix the logical replication timeout during large DDLs.
- 8c58624df462 16.0 landed
Fix the logical replication timeout during large transactions.
- f95d53eded55 15.0 landed
- d6da71fa8f28 14.4 landed
- 55558df23741 13.8 landed
- f832b5007c1c 12.12 landed
- 87c1dd246af8 11.17 landed
- a4015ec0375d 10.22 landed
Rethink the delay-checkpoint-end mechanism in the back-branches.
- 10520f434687 14.3 cited
Revert "Logical decoding of sequences"
- 2c7ea57e56ca 15.0 cited
Skip empty transactions for logical replication.
- d5a9d86d8ffc 15.0 cited
Allow specifying column lists for logical replication
- 923def9a533a 15.0 cited
Add decoding of sequences to built-in replication
- 75b1521dae1f 15.0 cited
Fix ABI break introduced by commit 4daa140a2f.
- 56e366f6757d 13.4 cited
Lag tracking for logical replication
- 024711bb5446 10.0 cited