Re: Error: absolute path not allowed

From: wschwurack <wolf(at)uen(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Error: absolute path not allowed
Date: 2013-01-10 21:33:11
Message-ID: 1357853591596-5739598.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Stefan Keller 2013-01-10 22:36:38 Re: [postgis-users] Query with LIMIT but as random result set?
Previous Message Kevin Grittner 2013-01-10 20:28:23 Re: [postgis-users] Query with LIMIT but as random result set?