B-tree index bloat estimation
This file contains 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
| /* The bloat estimation queries moved to this respository: | |
| * https://github.com/ioguix/pgsql-bloat-estimation | |
| */ |
Hi darkixion,
Sorry for the late answer, I never noticed your comment.
As explained in my various blog posts, this table is using the "name" type, leading to really bad estimations. You have to filter out indexes that we can not have a good estimation using the "is_na" field.
See "Known bug" in http://blog.ioguix.net/postgresql/2014/06/24/More-work-on-index-bloat-estimation-query.html
I should add links to my blog posts as documentation or put these queries in a repository with a proper README at some point...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The bloat for pg_operator on a database I just looked at returned -80 as the bloat ratio with this query.