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 15:02:01 |
Message-ID: | 1357830121331-5739543.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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-01-10 07:42:03 MST [8555]: [-1] db=postgres, user=postgres,
client=10.11.0.200 STATEMENT: SELECT pg_read_file($1, 0, 1048576)
the client is the database server
I ran the query, no rows found
postgres=# select proname from pg_proc
postgres-# where prosrc like '%pg_read_file%'
postgres-# and pronamespace=(select oid from pg_namespace where
nspname='public');
proname
---------
(0 rows)
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Error-absolute-path-not-allowed-tp5739320p5739543.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | wschwurack | 2013-01-10 15:14:17 | Re: Error: absolute path not allowed |
Previous Message | Fujii Masao | 2013-01-10 14:50:31 | Re: [Solved] Corrupt indexes on slave when using pg_bulkload on master |