Theo Schlossnagle recently wrote a blog post called seven things. The idea is, seven things that you "might" want to know about him. Along those lines he listed me as someone he would like to know seven things about. It has taken me a while to get to the post because I have been busy with variousthings. So here we go, seven things about me.
I think the Open Source community needs to learn when to be quiet.
I hate it when people think I should care about x.
I spent two recent years being someone, I am not. This problem has been resolved.
The second part of this blog is I am supposed to list seven people I would like to know seven things about. This has struck me as more difficult than I imagined. Most of the people I want to know about, don't blog and barely email. Many other people don't interest me. Here we go:
There has been a lot of talk through the years of what the minimum set of hardware requirements are for a PostgreSQL database. Generally speaking the requirements for PostgreSQL are very low, you can even get by on 256 Megs of memory. However you rarely hear or read about what would be considered the minimum production hardware requirements for PostgreSQL.
A primary reason for this is that every business has their own requirements and thus one persons minimum requirements are not another persons minimum requirements. Of course since we are in geek world and many geeks are uniquely pedantic and unable to see outside of their own bubble, my requirements may be wrong without any understanding of business requirements as a whole. So what do we do? We voice our opinion anyway.
After years of listening to Dave Page, Magnus Hagander, Josh Berkus, David Fetter, Stefan Kaltenbrunner, Ads, Gabrielle, JPA and numerous other contributors that I should mention but won't. I have finally submitted to get a passport.
I recently configured a complete Pylons + PostgreSQL environment for a customer. The operating system was (of course) Ubuntu Hardy. The system included the use of Simpycity and WSGI. Although I could never done it without the Pylons documentation, I found that it was unnecessary complicated for those who just want to get it done.
PostgreSQL Conference East is being held at historic Drexel University on April 3rd through 5th 2009 . This is the second call for papers. The call for papers ends Feb 23rd and speakers will be notified on the 27th. You may submit your talk here. We are looking for a wide range of topics. Can you speak on any of the below topics? What about a different topic? As long as it is centered around PostgreSQL we want to hear about it.
C Function development
Writing Procedural Languages
Explaining the process model
Backing up PostgreSQL
Understanding and Configuring Autovacuum
Trigger Happy (how to use triggers)
PITR -- happiness is a shipped transaction log
User / Groups / Roles
End User development:
Web Frameworks with PostgreSQL
Do you have a successful case study to present?
How did you solve a problem with PostgreSQL?
Do you have an Open Source product that runs on PostgreSQL?
As always we let the presenters drive the feel of the conference. If you have
an itch, let's figure out how to scratch it (as long as it is with PostgreSQL).
Submit your paper today.
Last Saturday I gave a talk at the Northwest Python Day in Seattle. Unfortunately it was a short talk of only 30 minutes so I didn't get to cover all the topics I wanted but I was able to briefly share on PostgreSQL and on configuring PostgreSQL (Mammoth) Replicator. Just for grins I started the talk off with a question, "Please raise your hand if you are running Ubuntu." There were over 50 people in the room. Over half raised their hand. World domination is coming along nicely.
I was asked two questions at the end of the talk. One was about how to have many masters replicate to a single slave. Similar to the salesman problem where they have a database of information that has to sync up to the main hub once a day or something like that. This particular application was doing security polling and the gentlemen wanted to have all the nodes report centrally. Replicator isn't really designed for that. I suggested looking at Slony which is a little more flexible with obscure configurations. The second question was about the mcp server and if the master/slaves would recover should the mcp be unavailable for a period of time. Yes, they will.
The trip itself was pretty uneventful but it was nice to get out of town for a couple of days.