Postgres Housekeeping

Shady — Mon, 29 Jan 2007 07:30:00 -0800

Previously, we installed postgresql on our OS X computers. Now lets do a little bit of house keeping and clean up to make it more convenient for general use.

We'll start with the easiest problem first - getting rid of that postgres user hanging around our login window. One simple command takes care of this:

sudo defaults write /Library/Preferences/com.apple.loginwindow HiddenUsersList -array-add postgres

You'll be prompted for your administrator password, and after this command executes, postgres will no longer show up in the login window. You will, however, notice an option "Other..." so you can still login as the postgres user if you wish. This will not affect your ability to use su or sudo and execute commands as the postgres user.

Next task is to get postgres to start up on its own. For this, we will use the newfangled technology provided by apple in 10.4: Launchd. Fortunatley, lots of smart (and not lazy) people have done the hard work for us. You can download a functional launchd item here

Note that the fine gentleman who made this Launchd item has his own tutorial for setting up postrgres. Check if out, if you like. There is a lot more detail to be had there, such as setting up perl and java to connect to postgres. However, his installation direction for postgres different then the one we used previously. As a result this we will need to change a few properties of this plist. An aside: since launchd items are just plists (xml files) we can use the plist editor that comes bundled with xcode tools to edit the file. And this works. A nice alternative, however, is the nifty little tool Launchd Editor, available here. Back to the action: we need to change the following properties of the plist file:

The value for -D should be /usr/local/pgsql/data (or where ever you set your data directory)
The value for log_directory should be /usr/local/pgsql/logs (or, again, where ever you set your logs directory).

Once we have made the proper changes, save the plist and fire up the terminal. We're just a few steps away from having postgresql run whenever we want it to. The following commands will finish this job for us:

sudo cp org.postgresql.postmaster.plist /Library/LaunchDaemons
sudo launchctl load /Library/LaunchDaemons/org.postgresql.postmaster.plist

At this point, launchd knows all about our new item, and all we have to do is tell it to start:

sudo launchctl start org.postgresql.postmaster

And with that, postgres should be up and running. Fire up Activity Monitor and check for the postgres process. You should see a few. If we want to stop the service, run the same command as above, but replace start with stop. Pretty straightforward. I like to set up two aliases in my .alias file for starting and stopping the service easily from the command line.

And there we are. We can nicely start and stop postgres, the user is gone from our window, and all is right with the world. If only we had some kind of GUI management tool for dealing with postgres . . . something like, oh, I dunno . . . .this, maybe?. Of course, if you're more partial to web based management solutions a la phpmysql, there is always phpPgAdmin.

Of course, we still only have on user set up . . . we have to use postgres to log in to our database. While I won't tell you exactly what you need to do in order to set up a new user, I will give you a hint: check the excellent postgres documentation for create role. With the documentation on that, and the GUI editing tool of your choice (or good ol' psql) you should have extra users up and running in no time. The LOGIN attribtue might help too.

Tune in next time, when we (finally!) get around to installing PostGIS.

Shady Project: Tag Postgres

Postgres Housekeeping