I used to have to keep an eye on tuple table bloat for awhile on big PG databases, but with recent versions of Postgres the auto-vacuuming has mostly kept it in check for all but the most gargantuan, busy tables. I pretty much have stopped caring (and I cared a lot less when SSDs became the default as the fragmentation penalty that a full repack would fix wasn't as bad as it was during the spinning metal days).
Index bloat has been another story, though. Pruning b-trees is expensive and I've mostly just been scheduling reindexes (which have been able to be done concurrently for awhile) instead.
USING INDEX is interesting, though...