I found what pg_read_file didn't like. With the help of enterprisedb support which gave me the steps to see what was wrong 1. set log_min_duration_statement = 0 in postgresql.conf: This will log all statements 2. select pg_reload_conf(); reloads the parameters 3. Wait until the error message come up again. The problem was I had set parameter hba_file to the soft link. I change the parameter to the correct path which fixed the problem. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Error-absolute-path-not-allowed-tp5739320p5739598.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
