---
title: "This Week's PostgreSQL News (#64)"
publication: "Postgres Weekly"
issue: 64
published_at: "2014-07-09"
canonical_url: "https://postgresweekly.com/issues/64"
---

Postgres Weekly Issue 64 - July 9, 2014

[Archives](http://postgresweekly.com/issues) [Read this issue on the Web](http://postgresweekly.com/issues/64)**Postgres Weekly****Issue 64**
July 9, 2014As always, thanks to [Craig Kerstiens](https://twitter.com/craigkerstiens) for continuing to curate Postgres Weekly for us :-) Be sure to hit him up on Twitter with any appreciation or ideas.[You (probably) don't need NoSQL (with Postgres)](http://www.slideshare.net/EnterpriseDB/postgresadvancesno-sqlmay2014?utm_source=postgresweekly&utm_medium=email)Hearing the case for somewhere in your team that you need NoSQL? Let’s dissect the case for what NoSQL really is, and further where you may need it or where PostgreSQL (which you hopefully have already deployed) can fill that gap._Bruce Momijan_[PostgreSQL Performance on Docker](http://www.davidmkerr.com/2014/06/postgresql-performance-on-docker.html?utm_source=postgresweekly&utm_medium=email)Thinking about running Postgres within Docker vs. LXC yourself? You don’t have to run those performance tests yourself, here’s an initial look with some surprising results, at least for the author._David Kerr_[Postgres 9.5 feature highlight: WHERE clause pushdown in subqueries with window functions](http://michael.otacoo.com/postgresql-2/postgres-9-5-feature-highlight-where-pushdown-with-window-function/?utm_source=postgresweekly&utm_medium=email)Window functions are great and super powerful for anyone doing complex analysis with queries, but sometimes they’re not the most performant thing you can do. In some cases you may not know what the most performant thing is, but here’s a case in 9.5 where it may automatically become more performant for you, and of course some fun details behind it._Michael Paquier_[Postgis, PostgreSQL's spatial partner Part 3](http://shisaa.jp/postset/postgis-postgresqls-spatial-partner-part-3.html?utm_source=postgresweekly&utm_medium=email)Continuing from the past two issues, here’s the next in the series regarding geospatial and Postgres. This one extends on a real world use case, along with digging in on performance optimization._Tim van der Linden_[[CVE-2014-3482 and -3483\] Two ActiveRecord SQL Injection Vulnerabilities Affecting PostgreSQL](https://groups.google.com/forum/#!topic/rubyonrails-security/wDxePLJGZdI?utm_source=postgresweekly&utm_medium=email)SQL injection attacks are a long standing (but hopefully) problem for so many apps, though if you’re running Rails and/or ActiveRecord, here’s a few you should pay attention to and check if you’re vulnerable. [New versions of Rails](http://weblog.rubyonrails.org/2014/7/2/Rails_4_0_8_and_4_1_4_have_been_released/) have been released to resolve the issue._rubyonrails-security_[Store an array in PostgreSQL hstore in Rails4](http://blog.brzezinka.eu/rails4/store-an-array-in-postgresql-hstore-in-rails4?utm_source=postgresweekly&utm_medium=email)Both the array type and hstore can be super powerful within Postgres, here’s a great dive how you can use both of them natively within Rails._Grzegorz Brzezinka_Curated by [Craig Kerstiens](http://craigkerstiens.com/) and published by [Cooper Press](https://cooperpress.com/).
Want to sponsor an issue? See our [media kit.](https://cooperpress.com/mediakit2014q2.pdf)

 © 2017 Cooper Press Ltd. [Email policy](https://cooperpress.com/spam.html) [Privacy policy](https://cooperpress.com/privacy.html)
Office 30, Fairfield Enterprise Centre, Louth, LN11 0LS, UK[Update your email address](*|UPDATE_PROFILE|*)
or [unsubscribe here](*|UNSUB|*)