From cc282844868c9449dfb54eee781bb6c36df96743 Mon Sep 17 00:00:00 2001 From: Nikolas Date: Wed, 11 Dec 2024 08:39:59 +0100 Subject: [PATCH] Update 600-faq.mdx (#6512) --- content/400-pulse/600-faq.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/400-pulse/600-faq.mdx b/content/400-pulse/600-faq.mdx index 216367482a..3078bb66fa 100644 --- a/content/400-pulse/600-faq.mdx +++ b/content/400-pulse/600-faq.mdx @@ -169,4 +169,10 @@ A large WAL backlog indicates that Pulse is unable to connect to the publication ### Can users manually set up replication slots for Prisma Pulse? -Yes, users can manually create and manage replication slots. However, Pulse does not maintain self-managed slots. For optimal performance, we recommend using the slots configured by Pulse during the initial setup. \ No newline at end of file +Yes, users can manually create and manage replication slots. However, Pulse does not maintain self-managed slots. For optimal performance, we recommend using the slots configured by Pulse during the initial setup. + +### Can there be problems if I manually configure the `walsender_timeout`? + +The `walsender_timeout` configuration parameter is a timeout setting that determines the maximum amount of time a WAL sender process (used in replication) will wait for a response from a WAL receiver before disconnecting. It usually defaults to 60 seconds. + +Setting a value smaller than 10 seconds may cause connection issues with Pulse.