I do not think that this module should do any SQL at all.  Fetching a raw crash is already implemented in the crashstorage class and it takes partitioning into account - we ought to avoid reimplementing functionality that exists elsewhere.  In fact, this module could be identical with the module of the same name in the ```fs``` package.  Further, if they're the same, with only the crashstorage instance different, they could be combined into one "crash_data" module. That would also enable _any_ crashstorage implementation (fs, postgres, hb, ...) to serve as a data source for this service without having to do additonal coding.