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

Heap_bloat/Btree_bloat : Lock_timeout and not statement_timeout #1381

Open
Krysztophe opened this issue Apr 15, 2024 · 0 comments
Open

Heap_bloat/Btree_bloat : Lock_timeout and not statement_timeout #1381

Krysztophe opened this issue Apr 15, 2024 · 0 comments
Assignees

Comments

@Krysztophe
Copy link
Contributor

The current btree_bloat (and probably others ?) have statement_timeout = 30s.

It would be cleaner to have lock_timeout too, to a much lower value (eg 3s).
If the probe fails, I'd like to know if this comes from a very heavy lock on the tables, or from the probe's duration.

PS1 : is there any way to customize the timeouts ?

PS : statement_timeout (and lock_timeout) values should appear in the error messages.

@daamien daamien self-assigned this Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants