Re: fetch_search_path() and elog.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: nonsolosoft(at)diff(dot)org
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: fetch_search_path() and elog.c
Date: 2005-07-11 13:25:30
Message-ID: 7724.1121088330@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ferruccio Zamuner <nonsolosoft(at)diff(dot)org> writes:
> I need to have in the log_line_prefix the search_path where the query
> has run.
> So last week I've started to read elog.c and I was thinking about a
> small patch there using a new "%S" option.

There's no chance of that code working when not inside a transaction;
which means that in most of the scenarios where you really want a log
entry to be made, it will fail.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bhanu Prakash 2005-07-11 13:25:59 About postgres C++ APIs...
Previous Message Andrew Dunstan 2005-07-11 13:14:46 Re: suspicious pointer/integer coersion