| Postgres Weekly |
Issue 11
May 22, 2013
|
|
|
Featured
| JackDB: Database Development in the Cloud |
|
One of the most common requests for new Postgres users is what admin interface to use. I previously wrote about how I work with psql, but a CLI isn't for everyone. If you need more of an traditional GUI give JackDB a try, it's a great Web interface for interacting with your Postgres database.
|
|
From our sponsor
| Heroku Postgres - Fully managed Postgres on EC2 |
There's a lot to worry about when building your application; ensuring your database is secured, backed up, available shouldn't have to be part of that. Let Heroku Postgres focus on keeping your database running so you can take advantage of all the awesome features within Postgres.
Heroku Postgres is the worlds largest provider of Postgres as a Service, offering fully managed databases on top of EC2. Get started today for free and scale easily as your application needs to.
|
|
 |
The rest
| Postgres Common Table Expression Super Example |
|
Common Table Expressions or CTEs make SQL almost readable. If creating anything more than an extremely simple query CTEs will help create SQL that can be understood by others as well as you at a future time. Here's a great example which also includes window functions to highlight the power of Postgres.
|
|
| PostgreSQL 9.3 beta: Federated databases and more |
|
Foreign Data Wrappers (or FDWs) have already provided a lot of flexibility for Postgres with previous releases. Whether querying Redis, Mongo, or Twitter from Postgres they enable a whole new set of use cases. With Postgres 9.3 comes the Postgres FDW which enables a world of federated Postgres databases.
|
|
| Postgres Fuzzy Search Using Trigrams (+/- Django) |
|
An interesting trial and mostly failure at taking advantage of trigrams for using spelling correction within an application. In particular this takes advantage of it within Django though it's not heavily coupled inside the framework and applies to most languages.
|
|
| Call me maybe: Postgres |
|
As part of a broader series on network partitions @aphyr takes a look at Postgres. While it typically falls under the always consistent category there's at least some very little gray area in here. Read more on how Postgres measures up with regards to network partition failures.
|
|
|
|
|