A better approach, I think, would be a tool that takes an SQL log and figures out the optimal indexes based on those SQL statements. It could run "explain" statements on the recorded queries to determine which columns need indexes, including ones that are queried together, which would benefit from multi-column indexes. The "explain" output would also give some information about common filter values which could be used to generate partial indexes.
Another way would be to use genetic algorithms to create random indexes, run the queries on a dummy database, and then read the index usage stats to determine the most efficient combinations.
What would be lovely is a tool that you could run autonomously every week or month, and which would simply add/remove indexes as it sees fit.
The ultimate solution would be for Postgres itself to figure out and report potential plan improvements. After all, the planner knows best.