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
Charge only server memory for dictionaries #49995
Conversation
This is an automated comment for commit 0586a27 with description of existing statuses. It's updated for the latest CI running
|
5dbe8e1
to
bdda4d7
Compare
Right now the memory will be counted for query/user for dictionary, but only if it load by user (via SYSTEM RELOAD QUERY or via dictGet()), but it could be also loaded in backgrounad (due to lifetime, or update_field, so it is like Buffer, only server memory should be charged. v2: mark test as long Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com> Co-authored-by: Sergei Trifonov <svtrifonov@gmail.com>
Should be a problem only for upgrade check, in upstream it should be fixed already - #49106 |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Charge only server memory for dictionaries
Right now the memory will be counted for query/user for dictionary, but only if it load by user (via SYSTEM RELOAD QUERY or via dictGet()), but it could be also loaded in backgrounad (due to lifetime, or update_field, so it is like Buffer, only server memory should be charged.