Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 600-faq.mdx #6512

Merged
merged 1 commit into from
Dec 11, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion content/400-pulse/600-faq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
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.
Loading