Looks like the issue was a postgres configuration mess. Now that that's been sorted...
Hello! I've just finished installing ]po[ 4.0.5 on a CentOS 6 with Postgres 8.4 system....