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

Postgres Weekly Issue 57 - May 8, 2014

[Archives](http://postgresweekly.com/issues) [Read this issue on the Web](http://postgresweekly.com/issues/57)**Postgres Weekly****Issue 57**
May 8, 2014[Postgres Datatypes – The ones you're not using](http://www.craigkerstiens.com/2014/05/07/Postgres-datatypes-the-ones-youre-not-using?utm_source=postgresweekly&utm_medium=email)Postgres has a broad range of datatypes in addition to the usual suspects (int, numeric, varchar). While not always applicable for all apps, when you do need them they can be extremely handy._Craig Kerstiens_[Why you should always set temp_file_limit](http://www.databasesoup.com/2014/05/why-you-should-always-set-tempfilelimit.html?utm_source=postgresweekly&utm_medium=email)Want to keep a query from a user from potentially crashing your entire database? This setting can be extremely handy for just that, and should be a requirement on any production database._Josh Berkus_[Postgres partitioning explained](https://github.com/fiksu/partitioned/blob/master/PARTITIONING_EXPLAINED.txt?utm_source=postgresweekly&utm_medium=email)Been curious about partitioning data within Postgres, but confused? You’re probably not alone, here’s a transcript from a conversation that sheds quite a bit of light on how it works._Keith and Aleksandr_[Trigger Overhead](http://www.openscg.com/2014/05/trigger-overhead/?utm_source=postgresweekly&utm_medium=email)Triggers have quite a few use cases and provide plenty of value, but if you use them in multiple places there’s a few things that can lessen their overall impact. Here’s a look at the performance overhead of triggers and how you can better utilize them._Jim Mlodgenski_[New Finding Unused Indexes Query](http://www.databasesoup.com/2014/05/new-finding-unused-indexes-query.html?utm_source=postgresweekly&utm_medium=email)Finding unused indexes in Postgres can be extremely handy. For each index you have it takes up some space on disk and slows down write throughput. If you’ve got one that is unused its simply a waste, here’s a query that helps on newer Postgres versions identify such._Josh Berkus_[A full text search engine in Postgres (Part 2)](http://shisaa.jp/postset/postgresql-full-text-search-part-2.html?utm_source=postgresweekly&utm_medium=email)A follow on to last week here’s a deeper dive on using full text search in Postgres. This one gets a bit more advanced than the generic case, which will typically work for most._Tim van der Linden_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|*)