Keith Fiske

Hmm... I'll have to see about exempting them for now. There's another function in pgstattuple that works with gin indexes, but not sure how to interpret its stats as it...

Just curious... for the index you believe is bloated, can you run `pgstatginindex()` on it and share the results? I don't have any clients using GIN indexes at the moment...

Ok. I'll see if I can figure anything out. For now just working on a patch to leave GIN indexes out. Thankfully GIST seem to work.

If you come across any queries that are useful for determining GIN bloat, please share. :)

Released version 2.0.1 that filters out GIN indexes from scanning so it doesn't error out anymore. Thanks for reporting the issue! Hopefully find something that works eventually.

Pushed a fix to branch https://github.com/keithf4/pg_bloat_check/tree/2.7.1 Found a few other spots that were missing the conversion as well. Let me know if that works ok now.

Released version 2.7.1 with fix. Thanks for reporting and testing!

A request for renewed interest in getting this enchancement. Could use it for constraint stuff in pg_partman.

Wish I had the time. Just letting you know there is interest in this feature. :)

Sorry for the delay. This has been fixed in the new release for 4.7.1