Andrew Dunstan wrote:
> >> defaulting to the beginning if not found.
> >> Examples: "%T [%P]: " (everybody gets timestamp and pid)
> >> "%T [%P]: [EMAIL PROTECTED](%C:%S %I line:%L %X%T [%P]:" (same
> >> effect
> >> as example under previous point)
> >> - something
Bruce Momjian said:
> Andrew Dunstan wrote:
>>
>> I haven't had any other feedback on this patch that I posted. However,
>> I'm a bit dissatisfied with it for a couple of reasons:
>>
>> . when a connection is logged we don't yet know the user and database,
>> because we haven't processed the init
Andrew Dunstan wrote:
>
> I haven't had any other feedback on this patch that I posted. However,
> I'm a bit dissatisfied with it for a couple of reasons:
>
> . when a connection is logged we don't yet know the user and database,
> because we haven't processed the initial packet yet. That cause
I haven't had any other feedback on this patch that I posted. However,
I'm a bit dissatisfied with it for a couple of reasons:
. when a connection is logged we don't yet know the user and database,
because we haven't processed the initial packet yet. That causes %U and
%D to produce empty strin
Tom Lane said:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>> I am about to redo the patch that would allow tagging of log lines
>> with info via a printf-style string.
>
>> Any comments or suggestions before I start?
>
> I think Bruce already applied the previous version of your patch.
Not that
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I am about to redo the patch that would allow tagging of log lines with
> info via a printf-style string.
> Any comments or suggestions before I start?
I think Bruce already applied the previous version of your patch. No
problem with yanking it out f
Joshua D. Drake wrote:
Andrew Dunstan wrote:
I am about to redo the patch that would allow tagging of log lines
with info via a printf-style string.
Current plans are to call the config parameter "log_line_info" and
implement the following escapes:
%U = user
%D = database
%T = timestamp
%P
Joshua D. Drake wrote:
> Andrew Dunstan wrote:
> >
> > I am about to redo the patch that would allow tagging of log lines with
> > info via a printf-style string.
> >
> > Current plans are to call the config parameter "log_line_info" and
> > implement the following escapes:
> >
> > %U = user
>
Andrew Dunstan wrote:
I am about to redo the patch that would allow tagging of log lines with
info via a printf-style string.
Current plans are to call the config parameter "log_line_info" and
implement the following escapes:
%U = user
%D = database
%T = timestamp
%P = pid
%L = session log line
I am about to redo the patch that would allow tagging of log lines with
info via a printf-style string.
Current plans are to call the config parameter "log_line_info" and
implement the following escapes:
%U = user
%D = database
%T = timestamp
%P = pid
%L = session log line number
%C = sessionid
Andrew Dunstan wrote:
> Rod Taylor wrote:
>
> >>and I'm willing to entertain other suggestions.
> >>
> >>
> >
> >Very nice, but you missed the most important. Command Tag.
> >
> >
>
> I've had a brief look at this proposal (to allow reporting of the
> command tag along with username, datab
Rod Taylor wrote:
and I'm willing to entertain other suggestions.
Very nice, but you missed the most important. Command Tag.
I've had a brief look at this proposal (to allow reporting of the
command tag along with username, database, session cookie etc on each
log line). I'm wondering wh
12 matches
Mail list logo
