On Tue, Aug 26, 2014 at 5:44 PM, Keith Fiske <keith@xxxxxxxxxx> wrote:
Is that a typo? It seems to be looking for the 32bit version of mingw but the 64-bit version when compiled elsewhere. The heroku version just sets this value to 4 outright (since they know what they're running). I tried changing this value to see if it made a difference, but it doesn't seem to.I've tried decoding these queries to understand what they're actually doing, but they're both quite a bit over my head. I did notice one thing in the check_postgres one:A client however, showed me that running the bloat check from heroku brings back some additional results. The additional results are actually tables we were kind of expecting to see that the check_postgres query does not return.So I recently wrote this script to help us in monitoring for table/index bloatI based my query off of the one contained in check_postgres, since I thought it seemed fairly accurate with what I was expecting to get back.
https://github.com/keithf4/pg_bloat_check
https://github.com/bucardo/check_postgres/blob/master/check_postgres.pl#L3512
CASE WHEN v ~ 'mingw32' OR v ~ '64-bit' THEN 8 ELSE 4 END AS ma
Anyone that's better able to evaluate which one of these two bloat check queries is more accurate able to provide some assistance?
Helps if I include the query from Heroku
https://github.com/heroku/heroku-pg-extras/blob/master/lib/heroku/command/pg.rb#L438-L504
