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

Double max_locks_per_transaction #134

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

adolsalamanca
Copy link
Contributor

After our last maintenance event, we have realized that current defaults do not suffice, specially for big dbs.
Given that, We're doubling what we assign in our tuner.

After our last maintenance event, we have realized that current defaults
do not suffice, specially for big dbs.
Given that, We're doubling what we assign in our tuner.
Copy link
Member

@alexeyklyukin alexeyklyukin left a comment

Choose a reason for hiding this comment

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

Looks good!

Since we have a primary (PR) -> read replica (RR) dependency on this parameter (RR should be always >= PR), the tuner settings will come into effect on PR with RR only after RR is tuned, so it may take two tunable events (i.e. resize) for the changes to come into effect.

@adolsalamanca adolsalamanca merged commit 154501b into main Mar 27, 2024
3 checks passed
@adolsalamanca adolsalamanca deleted the adol/double-max-locks-per-transaction branch March 27, 2024 15:07
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.

None yet

3 participants