Skip to content

Conversation

@AArdeev
Copy link
Contributor

@AArdeev AArdeev commented Jun 18, 2025

@AArdeev AArdeev requested a review from tecl1s June 18, 2025 06:42
@AArdeev AArdeev self-assigned this Jun 18, 2025

The default ``replication_sync_timeout`` value is going to be changed in future versions from ``300`` to ``0``.
You can learn the reasoning behind this decision from the :ref:`Default value for replication_sync_timeout <compat-option-replication-timeout>` topic, which also describes how to try the new behavior in the current version.
The default ``replication_sync_timeout`` value can be changed to 300 by using the ``compat`` module.
Copy link

@tecl1s tecl1s Jun 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It creates the erroneous impression that only two values are possible: 0 and 300. This is not the case. I think it would be better to avoid "300" and replace it with "old value" or similar. The link provided to compat option will reveal the necessary details.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, thank you!

@AArdeev AArdeev requested review from tecl1s and xuniq June 19, 2025 09:34
@AArdeev AArdeev force-pushed the AArdeev/gh-5183-fix-default-timeout-value branch from dc37181 to 4ca4ddc Compare June 20, 2025 05:15
@AArdeev AArdeev merged commit 18071dd into latest Jun 20, 2025
1 check passed
@AArdeev AArdeev deleted the AArdeev/gh-5183-fix-default-timeout-value branch June 20, 2025 05:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix default value in replication_sync_timeout

4 participants