"[R]equiring server installations..." I can only imagine you're used to working with flatfiles from that line ;). I'm mainly going to mirror Thraxil here, I've worked with Oracle, DB2, and PostgreSQL extensively and PostgreSQL does have a rather light maintenance load.
in reply to Re: Re: Sysadmin Aspects of DBMS
in thread Sysadmin Aspects of DBMS
How much work needs to go in will of course depend on your load, dataset, and the equipment you're running on. For many the defaults will be sufficient. Personally, even for light loading, I like spending a bit of extra time on install and tweaking everything to the hardware. Obviously you can do quite a bit partitioning, managing tablespace, etc. but
From the sound of your data/load setting up a couple cron jobs and applying the occasional patch will probably be all the sysadmin work you'll need to invest in it. VACUUM and VACUUM ANALYSE (or the command line wrapper vacuumdb as noted by Thraxil) and some backup cron jobs will probably be the extent of your involvement.
If you're going to be the DBA as well then an occasional audit of expensive queries (using EXPLAIN) and indices maintenance will often prove fruitful; though not required unless you're experiencing poor performance. Again, this is based on what you've said of your application.
To get a peak at the O'Reilly book before it's published (or to preorder), Command Prompt (the writers) have it online here. Bruce Momjian's PostgreSQL: Introduction and Concepts is also available online. And you can of course always read the official Administrator's Guide.
P.S. You may want to ask the editors to put an [OT] in the title of the post.