Thanks for the report – just had a look and it seems like Prodigy is currently expecting a name as the database name, which is passed in as the dbname or database parameter. If none is found, it defaults to prodigy. So simply removing that line from your config should do as a quick workaround for now.
Just fixed this and the update will be included in the next release. Prodigy will now check for a name, dbname or database setting and use that instead.
Speaking of PostgreSQL: There seem to be another issue with the ORM at the moment that causes requests to fail, as PostgreSQL complains if a relation already exists – unlike SQLite (see my comment over here for more details). This will also be fixed asap!