This has been tested using PostgreSQL 9.1 however it should work with earlier versions as well. If you'd like a graphical interface, try pgAdmin III. You'll need access to the psql however. This can be done either at the command line by entering:
psql -U postgres -h 127.0.0.1 -p 5432
You can of course log in with another account that has create database and create login priviledges.
From pgAdmin III, simply select any database and then click on PSQL Console from within the Plugins menu.
Before running the installation script you will have to edit it slightly to adjust some directory paths to match the location of your files. Also, it's highly recommened that you change the kbadmin password while you're at it from the purposely obnoxious PHP_is_Right_Out! to something clever that you'll remember but someone else isn't likely to guess.
Search and replace: /home/ddrouin/pykb-code with the directory that your place your copy of the source into.
Once that's done you're ready to go. Enter the following command, replacing your source directory location accordingly:
\i /home/ddrouin/pykb-code/pykb/sql/postgresql/install.sql
This will create the kbadmin user with the password you specified, the killboard database along with the ccp and pykb schemas. The ccp schema is a scaled down version of what's provided in CCP's Static Data Export (SDE) with table and column name formats changed to match with this project's naming convention.
Before adding any kill mails into your database you'll most likely want to have pricing data present - see [Updating Prices] along with [Aggregation] running so that summary tables will be kept up to date.
Edit this file to see the proper connection string info to reach the killboard database as kbadmin:
/home/ddrouin/pykb-code/pykb/conf/pykb.yml
Ensure that the MySQL related section is commented out or deleted.
You can move the config file elsewhere but if you do so then you'll need to specify a -c parameter when running the utility modules to inform them of the location of your config.