>> 1. Source control. Code at the level of PG/SQL into source control isn't as easily deployed and managed as, say, Java code. Not entirely true, PG extensions

>> 1. Source control. Code at the level of PG/SQL into source control isn't as easily deployed and managed as, say, Java code. Not entirely true, PG extensions can be versioned/packaged and deployed just like any versioned code. Just deploy the new version of the extension and ```drop extension foo; create extension foo``` to update to the new version. It's not as slick and greasy as ```git push heroku master```, but still, not so bad. (I'm not the author, but I have written a non-trivial Pl/PgSQL extension)