My tour this week of the PostgreSQL West conference has taught me that you can deliver three talks in two days, or you can have fun seeing other people's talks, but it's rather difficult to do both. My own talks are now uploaded to our talks page. You can also find the slides from Hannu's talk on Django/Python database calls, which unfortunately he was too ill to deliver in person.Out of the limited number of other presentations I did see, the standout for me was Nathan Boley's look at "Improving Planner Prediction Accuracy with Custom Selectivity Function". I'm hoping to take Nathan's new ideas for judging how close the PostgreSQL statistics match the underlying data and apply them to some difficult tables on a few client production systems.I'd also highly recommend
Since I've already pushed my book here once on my blog this week, this version will be short and include two chunks of free (as in beer) content for you. My book covering PostgreSQL performance, from versions 8.1 to 9.0, is now available.Downloads of the 468 page e-book text are available immediately from Packt Publishing. Publication of the associated code samples and shipping of printed copies will follow soon. There's even a free sample chapter covering Database Hardware, including critical information about how to keep your database writes safe with various types of disks and controllers. Secret for blog readers only: there's also an article about Server Configuration Tuning snipped from that chapter of the book you can read too."PostgreSQL 9
If you're looking for a heavy dose of information about PostgreSQL performance tuning, you're going to find the next month very interesting. We at 2ndQuadrant have been working on two books about PostgreSQL 9.0 this year. You can pre-order those right now, and as I'm staring at a home printed copy of my PostgreSQL 9.0 High Performance book right next to me at the moment, I can assure you that one is quite finished and soon to be released. Weighing in at a final count of 442 pages, I hope there's a few things there for just about everyone. I just read Simon and Hannu's PostgreSQL 9 Administration Cookbook over the weekend too, also due to be published soon, and it has a complementary set of information and a more task-driven focus.Since my head is just overflowing
Whether or not you made it our CHAR(10) conference last month, you can now relive part of the experience by downloading the conference slides. Some of those were posted live during the conference, some showed up later, but almost everything is there now. Sadly, Nic Ferrier's entertaining presentation about how WooMe was scaled up using Londiste and Django wasn't available in a form we could easily replay. For that one, you certainly did have to be there, in more ways than one.
The two talks I found the most informative were the updates on the states of pgpool-II and pgmemcache. Both those tools have that slightly frustrating combination of being really useful and a bit underdocumented relative to how complicated they are (in English at least!), so getting additional insight into them from
Officially Greenplum Database Single Node Edition (SNE) is only installable on Red Hat Enterprise Linux (RHEL) and SUSE Linux Enteprise Server (SLES), but while surfing the web I have seen many requests on how to install it on Debian/Ubuntu. Here I'm trying to give you some advices.
One of the main reasons users switch from other relational databases to PostgreSQL is the advanced support for geographic objects included in the PostGIS extension.
Being PostgreSQL specialists at 2ndQuadrant, we have tried to investigate if it was possible (and how) to install PostGIS on the Greenplum Single Node edition. Let's see how Marco Nenciarini, 2ndQuadrant consultant and a long time Debian developer, tried to do it.
Last week at the CHAR(10) conference we had a workshop on "Cloud Databases". To put it simply: what to do when the use case requirements exceed the resources available in the database server.
This was a main topic of the whole conference, and several solutions have been illustrated during the day. A common theme has been that no solution fits all the use cases, and that each solution comes with its cost; hence you have to choose the solution that your use case can afford.
This week I did something I'd prefer to never repeat: I left the country, did something useful, and made it back again in the same day. The occasion was the FreeBSD Developer Summit, held just before BSDCan--the convention that happens in Ottawa the week before PGCon every year. So I get to head right back again next week, but stay a while that time.The FreeBSD developers were nice enough to sponsor my trip so that we could talk about both the business and technical hurdles that I felt were keeping the sort of companies I work with from deploying their databases on FreeBSD more often than they do. My slightly updated slides are available on our talks page, I cleaned up a couple of things from what was presented (the most important rewording I'll talk about below).I
If you have a Linux server of the RedHat family (inclusing CentOS and Fedora), you might envy the way Debian/Ubuntu distributions handle PostgreSQL clusters management.
Although it is not easy to install different PostgreSQL versions on the same RedHat Linux server using RPMs, it is much simpler to install several instances of PostgreSQL (servers) and, at the same time, take advantage of the services infrastructure.
If you're running Linux, and particularly if you're running a database on Linux, it's been hard to recommend any filesystem other than plain old ext3 in recent years. Some of the alternatives that looked interesting at one point--jfs, ReiserFS--are completely abandoned at this point. The one that has been almost viable for some time now is XFS, originally an SGI projecs. And it's back to being in the limelight again this week.XFS had suffered from a number of problems in the past. Since it was designed for stable hardware, it wasn't as robust on standard cheap PC hardware at first; quite a bit of that was just cleaned up two years ago. It had this odd problem with zeroed files that scared some people off. It was treated as a second-class citizen in