rework how materialized views are updated

[natebrennand]

just noticed that Postgres actually lacks incremental updating of materialized views. this means that the materialized view tables are locked for the ~50 seconds that it takes to update them. this isn't really acceptable since it would just cause our queries to them to timeout.

---

proposed resolution:

1. remake materialized views w/ different names then rename them
   • would be done in a PG transaction (means every step works or no steps work)
   • would reduce the update time
   • still takes ~50 seconds
2. how many indexes can we add?
   • experiment and see if we can index enough things to make the materialized view creation faster
3. try a different database?
   • MySQL doesn't seem to have this from my brief googling (possibly with this plugin)
   • Oracle actually does have them (but there's licensing fees I think?)

---

CC @adicu/density @rbtying

[natebrennand]

to be considered:

views could be built from each other

hourly <- whole table
day <- hourly
week <- day
month <- week (probably won't be split properly, use day instead)?

This wouldn't fix the whole issue, but should make it significantly faster.

[natebrennand]

This still seems like a poor man's incremental update but it would accomplish what we need.

https://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.4#REFRESH_MATERIALIZED_VIEW_CONCURRENTLY