Postgres Cutover

[emonical]

In relation to #36, switching over to Postgres would provide substantial improvements, both in general performance, as well as in reduction of database locking.

Given the scope and complexity of the problem set, along with developing a solid cutover script, my recommendation is to do the following:

1. Take a snapshot of the database at a point in time,
2. Run the cutover script,
3. Do initial testing to get it to working,
4. Run it as a live/live with a staging-esque environment.

Ideally, at that point, have a group of people just go in and mess around with the data sets / commands, trying to break things / determine if things have broken.