Re: [PATCHES] WIP patch - INSERT-able log statements - Mailing list pgsql-hackers

From Guillaume Smet
Subject Re: [PATCHES] WIP patch - INSERT-able log statements
Date
Msg-id 1d4e0c10702191021t181d35fem19748dc4ec31a107@mail.gmail.com
Whole thread Raw
In response to Re: [PATCHES] WIP patch - INSERT-able log statements  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On 2/19/07, Alvaro Herrera <alvherre@commandprompt.com> wrote:
> If it adds necessary context then it clear does not have "the same
> behavior",

I mean log_line_prefix behaviour is the same. The other information
are syslog specific.

> I'd propose adding a log_entry_prefix separate from log_line_prefix; the
> entry prefix would contain most of the stuff, and log_line_prefix would
> be a minimal thing intended to be put in front of each _line_, so the
> example you show above could be

It could be a good idea.
It won't make me use stderr output but it will allow other people to
do so without any disadvantage :).

> Really, prefixing with a tab does not strike me as a great idea
> precisely because it's ambiguous.

Sure.

--
Guillaume


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: wishlist items ..
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_proc without oid?