/btree_bloat.sql
Last active Mar 28, 2018
| /* The bloat estimation queries moved to this respository: | |
| * https://github.com/ioguix/pgsql-bloat-estimation | |
| */ |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
darkixion
commented
Sep 17, 2014
|
The bloat for pg_operator on a database I just looked at returned -80 as the bloat ratio with this query. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
ioguix
Oct 8, 2014
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...
|
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... |
The bloat for pg_operator on a database I just looked at returned -80 as the bloat ratio with this query.