Every once in a while, a software developer releases a long-awaited update to much fanfare and user enthusiasm…and then it bombs miserably. We’re not saying that’s what happened with PostgreSQL, but just in case you didn’t love the way it runs after you updated it last, the publisher has released a new update that addresses most of the necessary bug fixes from the last update.

postgresql

And it’s not hard to give the folks at Postgre a break considering they’ve been offering one of the top open-source object relational databases for the last fifteen years. The database runs on all the major operating systems, has one of the most reliable architectures in its field, is fully ACID compliant and supports all foreign keys, and more.

So what was this bug that had everyone bemoaning the May 2015 update? It had to do with the file permissions. “The 2015-05-22 update release added an anti-corruption step which will fsync all files in the data directory on restart after a crash. This caused PostgreSQL to fail to start if it encountered any file permissions issues. The problem is now fixed.” There’s more specific information on the wiki about PostgreSQL, which can be found HERE.

Other than fixing that major hurdle, the developers also went ahead and addressed having the pg_get_functiondef() show the LEAKPROOF property, the pushJsonbValue() function push jbvBinary type, and allowing building with threaded Python on OpenBSD.

To be fair, the developers aren’t finished addressing some of the bugs and adding updates, but they wanted to get these things corrected right away for those users who’d downloaded the May update and were having issues. Another update is slated to come out in a few weeks, but these fixes were the top priority. To update to the June 4th release, you don’t have to do anything extreme, just power down PostgreSQL and update the binaries. If you haven’t updated in quite some time to one of the more recent versions, the process could be a little more involved but won’t be ridiculous and shouldn’t result in the loss of any info. To download the latest update for PostgreSQL from FileHippo, click HERE.