Hey all, so I'm one of the authors of postgression. The website isn't totally clear as to all the reasons why this may be useful. I've written a blog post about it, which you may also find helpful if you're interested:<p><a href="http://rdegges.com/postgression-a-postgresql-database-for-every" rel="nofollow">http://rdegges.com/postgression-a-postgresql-database-for-ev...</a>
I'm not convinced that the cumulative latency this would introduce into test runs is lower than the amount of time required to use brew or apt-get to install Postgres.
You know what would make this faster? If you ran your tests inside Heroku as well. Then you wouldn't have all the network round-trip time and you'd be test in the same environment you go to production on.
This may be a small nit, especially since this is specifically a public test facility. But you might want to restrict the guest roles to only access their own database public schema.<p>I can't see other's query activity, but I can see some of the pg_catalog tables.<p>For instance<p><pre><code> select count(*) from pg_stat_database;
count
-------
1900
(1 row)</code></pre>
Not sure I'd want to throw my schema out of our infrastructure.<p>At the moment, our integration test run takes nearly two hours but this is rolling out the schema and the sheer number of test cases (we have over 1 million lines of test cases). Something that speeds it up would be welcome but this is not for us.