postgres
Monitoring the Postgres Daemon
Following up on Running Postgres with Daemontools - Shutdown Errors, the Postgres mail list had some advice on monitoring and automatically restarting Postgres.
Running Postgres with Daemontools - Shutdown Errors
Running anything under daemontools seems like a great idea, but I've had a particularly bad time trying to shutdown postgres under daemontools while running Apache and PHP with persistent postgres connections.
Upgrading Postgres in parallel with your old version
Today I got caught up in PostgreSQL. A feature didn't work as planned and when the mailing list responded to my plea for help it turned out the feature didn't work fully in my version of Postgres, v.8.1.4.
Sad to say, I haven't compiled a pgsql version for 13 months. I got so lazy that the last time I installed on my dev machine I just used the package that came with Kubuntu. Now I'm in a bind. I have a production machine and a dev machine to backup, upgrade and restore.
I learned one important lesson in this and that is to name your postgres installation directory the same as the current version. That kind of goes against my best judgement but it means that you can run two Postgres instances beside each other. Why would you want to do that? Take this line from the upgrade instructions:
