Re: WIP patch - INSERT-able log statements

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: WIP patch - INSERT-able log statements
Date: 2007-02-19 17:00:17
Message-ID: 1d4e0c10702190900q2d9ac9acr555f6d99615d0230@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On 2/19/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> So add the session ID (%c) to log_line_prefix.

It could work if log_line_prefix was added before every line but it's
definitely not the case:
myuser mydb 45d9d615.4abe LOG: duration : 185.223 ms, statement : SELECT *
FROM lieu
LIMIT 10;
if you execute:
SELECT *
FROM lieu
LIMIT 10;

I worked a *lot* on query logging and I really didn't find any
solution to use stderr in a safe way, reason why I don't use it at all
and I don't recommend it (even if pgFouine supports it, it outputs a
warning as soon as the parser finds a multiline query).

--
Guillaume

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zoltan Boszormenyi 2007-02-19 17:13:03 How can I merge a TargetEntry with a tuple?
Previous Message Bruce Momjian 2007-02-19 16:52:28 Re: Chatter on DROP SOMETHING IF EXISTS

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2007-02-19 17:04:35 Re: Recalculating OldestXmin in a long-running vacuum
Previous Message Alvaro Herrera 2007-02-19 16:43:22 Re: WIP patch - INSERT-able log statements