Skip to content
This repository has been archived by the owner on Dec 17, 2024. It is now read-only.

[+] make unique dbname maintenance less costly for multi-daemon setups, fixes #525 #573

Merged
merged 1 commit into from
Dec 20, 2022

Conversation

kmoppel-cognite
Copy link
Collaborator

Only one instance can now have the lock for
admin.all_distinct_dbname_metrics maintenance. Not 100% perfect though as connections interrupts can still lead to multiple updates per day but still much more resource-friendly than current state.

#525

Only one instance can now have the lock for
admin.all_distinct_dbname_metrics maintenance. Not 100% perfect though
as connections interrupts can still lead to multiple updates per day but
still much more resource-friendly than current state.

#525
@pashagolub pashagolub self-assigned this Dec 16, 2022
@pashagolub pashagolub changed the title [+] Make unique dbname maintenance less costly for multi-daemon setups [+] make unique dbname maintenance less costly for multi-daemon setups, fixes #525 Dec 20, 2022
@pashagolub pashagolub merged commit 69588a0 into master Dec 20, 2022
@pashagolub pashagolub deleted the make-distinct-dbname-maintenance-less-costly branch December 20, 2022 11:10
pashagolub added a commit to cybertec-postgresql/pgwatch that referenced this pull request Feb 17, 2023
pashagolub added a commit to cybertec-postgresql/pgwatch that referenced this pull request Feb 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants