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
I added the values to log_line_prefix but this still doesn't give me anymore
info on why I'm getting the error
log_line_prefix = '%t [%p]: [%1-1] db=%d, user=%u, client=%h '
2013-01-10 07:42:03 MST [8555]: [-1] db=postgres, user=postgres,
client=10.11.0.200 ERROR: absolute path not allowed
2013-
I did some more debugging and found that I'm only getting the errors on the
databases that is being monitored by Postgres Enterprise Manager. I Will
have to contact EnterpriseDB support
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Error-absolute-path-not-allowed-tp57
On Thu, Jan 10, 2013 at 1:20 AM, wschwurack wrote:
> How do I find what is calling pg_read_file
>
>
As said, check the log's to find DB,Host,User etc. from where its been
called. If log_line_prefix not set to appropriate to all those details then
change it as shown below which just need RELOAD of
Look at your log line prefix setting in postgresql.conf. Specifically
log things like db, host, username, etc.
On Wed, Jan 9, 2013 at 12:50 PM, wschwurack wrote:
> How do I find what is calling pg_read_file
>
>
>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/Err
How do I find what is calling pg_read_file
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Error-absolute-path-not-allowed-tp5739320p5739424.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-gene
On Tue, Jan 8, 2013 at 8:39 PM, Wolf Schwurack wrote:
> I am getting a repeating error and not sure what why.
>
> ** **
>
> 2013-01-08 06:12:08 MSTERROR: absolute path not allowed
>
> 2013-01-08 06:12:08 MSTSTATEMENT: SELECT pg_read_file($1, 0, 1048576)
>
> 2013-01-08 06:42:10 MST
On Tue, Jan 8, 2013 at 8:09 AM, Wolf Schwurack wrote:
> I am getting a repeating error and not sure what why.
>
>
>
> 2013-01-08 06:12:08 MSTERROR: absolute path not allowed
>
> 2013-01-08 06:12:08 MSTSTATEMENT: SELECT pg_read_file($1, 0, 1048576)
>
> 2013-01-08 06:42:10 MSTERROR: absolute path
I am getting a repeating error and not sure what why.
2013-01-08 06:12:08 MSTERROR: absolute path not allowed
2013-01-08 06:12:08 MSTSTATEMENT: SELECT pg_read_file($1, 0, 1048576)
2013-01-08 06:42:10 MSTERROR: absolute path not allowed
2013-01-08 06:42:10 MSTSTATEMENT: SELECT pg_read_file($1,
