My slide presentation from PDX PG Day 2010 in Portland, Oregon.

The presentation was created in Open Office (the .ODP file - Postgresql (OSCON).odp), but I've also created a PPT version (Postgresql (OSCON).ppt) exported from Open Office.

I just completed a presentation for my local PostgreSQL User Group (the Portland PUG) and gave it last Thursday.  I need to add some updates to clarify things and round out some of it, but here it is as I gave it.

Hopefully there are others who will find it useful.

As a side note, there are NOTES on some of the slides to go along with the material being presented.

Sometimes I want to find out how many rows are in each user table in a SQL Server 2000 database. The following SQL helps me determine this.

If you have a dedicated database server and the partition with the MySQL database fills up (or starts getting low), you can move your MySQL databases to a different location.

Let’s say you want to move the database to /home/mysql

Sometimes, on a high-volume / high TPS database, I want to make sure I've made updates to ALL the recovers, and not leave some orphaned data out there. This usually occurs because someone has a locked record while they're making a change. So when I'm making updates to multiple records (remember, SQL is SET based, so it applies to all records that match a condition), I use a belt and suspenders approach.