I continue to try and get Atom setup in the most productive way - especially for Ruby programming. I continue to be impressed with the tool. For unit testing I favor MiniTest and I wanted a way to run tests from inside Atom without leaving the editor environment.
Lag came in handy again.
“Should any American soldier be so base and infamous as to injure any [prisoner]. . . I do most earnestly enjoin you to bring him to such severe and exemplary punishment as the enormity of the crime may require. Should it extend to death itself, it will not be disproportional to its guilt at such a time and in such a cause… for by such conduct they bring shame, disgrace and ruin to themselves and their country.” – George Washington
In a standard smallish Postgresql installation its actually fairly straightforward to figure out what indexes to create to eliminate sequential scans and improve your performance. But in a larger system where there are thousands of different queries, perhaps written by dozens of different engineers, the problem of addressing performance issues gets a bit more difficult. However, the same techniques can be used on both systems. I’ll describe what I use and perhaps it will be useful for someone else.
Some days you just want to know who is connecting up to your database. The following SQL works for 9.3 Postgresql.