Configure PostgreSQL

From DOC

In a later step, the Tolven configuration Manager will add SSL certificates to the postgres directory and add schemas to the PostgreSQL database. Here, you must configure postgreSQL to use SSL.

pg_hba.conf

Use Notepad or wordpad to modify postgreSQL/version/data/pg_hba.conf to allow network access to the database. JDBC, even from localhost, requires network access to the database. Documentation is included in that file. The uncommented line should look something like this:

# TYPE   DATABASE    USER        CIDR-ADDRESS          METHOD
hostssl  postgres    postgres    127.0.0.1/32          md5 

You are done with the pg_hba.conf file, although remember to change this file if you need to access postgreSQL from clients not on localhost. You can also change the TYPE from hostssl to host, which will allow connections via non-ssl clients, but this is not recommended.

postgresql.conf

Next, edit the postgreSQL/version/data/postgresql.conf file so that its security configuration enables SSL.

In the postgresql.conf file this line

# ssl = off 

should be changed to

ssl = on 

(remove the # and change off to on)

Version 8.4

When installing Version 8.4, the posgres.conf file, has a property value which leads to a warning message:

WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]
Could not find new XAResource to use for recovering non-serializable XAResource...

Change the max_prepared_transactions property to be greater than zero. For example:

max_prepared_transactions = 5 # zero disables the feature

You must restart the PostgreSQL server for this change to take effect.