MDB-32132: fix grantor selection for mdb_superuser#4
Merged
reshke merged 1 commit intoMDB_15_10_aqofrom Jan 17, 2025
Merged
Conversation
x4m
approved these changes
Jan 17, 2025
reshke
added a commit
that referenced
this pull request
Feb 11, 2025
reshke
added a commit
that referenced
this pull request
Feb 18, 2025
reshke
added a commit
that referenced
this pull request
May 6, 2025
reshke
added a commit
that referenced
this pull request
Aug 6, 2025
reshke
added a commit
that referenced
this pull request
Aug 6, 2025
reshke
added a commit
that referenced
this pull request
Aug 12, 2025
reshke
added a commit
that referenced
this pull request
Nov 8, 2025
reshke
pushed a commit
that referenced
this pull request
Nov 25, 2025
There've been a few complaints that it can be overly difficult to figure out why the planner picked a Memoize plan. To help address that, here we adjust the EXPLAIN output to display the following additional details: 1) The estimated number of cache entries that can be stored at once 2) The estimated number of unique lookup keys that we expect to see 3) The number of lookups we expect 4) The estimated hit ratio Technically #4 can be calculated using #1, #2 and #3, but it's not a particularly obvious calculation, so we opt to display it explicitly. The original patch by Lukas Fittl only displayed the hit ratio, but there was a fear that might lead to more questions about how that was calculated. The idea with displaying all 4 is to be transparent which may allow queries to be tuned more easily. For example, if #2 isn't correct then maybe extended statistics or a manual n_distinct estimate can be used to help fix poor plan choices. Author: Ilia Evdokimov <ilya.evdokimov@tantorlabs.com> Author: Lukas Fittl <lukas@fittl.com> Reviewed-by: David Rowley <dgrowleyml@gmail.com> Reviewed-by: Andrei Lepikhov <lepihov@gmail.com> Reviewed-by: Robert Haas <robertmhaas@gmail.com> Discussion: https://postgr.es/m/CAP53Pky29GWAVVk3oBgKBDqhND0BRBN6yTPeguV_qSivFL5N_g%40mail.gmail.com
reshke
added a commit
that referenced
this pull request
Dec 8, 2025
reshke
added a commit
that referenced
this pull request
Feb 6, 2026
reshke
added a commit
that referenced
this pull request
Feb 9, 2026
reshke
added a commit
that referenced
this pull request
Feb 9, 2026
reshke
added a commit
that referenced
this pull request
Feb 10, 2026
reshke
added a commit
that referenced
this pull request
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.