Re: Error: absolute path not allowed

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: wschwurack <wolf(at)uen(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Error: absolute path not allowed
Date: 2013-01-10 00:15:15
Message-ID: CAOR=d=0gA9XZAjrRck=Ya14UzighQV-zUFQyqAvbUm4pfKJudQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 <wolf(at)uen(dot)org> wrote:
> 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-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

--
To understand recursion, one must first understand recursion.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2013-01-10 00:21:33 Re: currval of sequence xxx_seq is not yet defined in this session?
Previous Message Ian Lawrence Barwick 2013-01-10 00:11:59 Re: How can I detect if a schema exists?