Skip site navigation (1) Skip section navigation (2)

Re: command tag logging

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: alvherre <alvherre(at)commandprompt(dot)com>
Cc: Ray Stell <stellr(at)cns(dot)vt(dot)edu>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: command tag logging
Date: 2010-05-27 16:49:49
Message-ID: 3713.1274978989@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-hackers
alvherre <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Ray Stell's message of mi may 26 17:08:33 -0400 2010:
>> I just installed a compiled from src 8.3.11.  I usually include %i, command tag,
>> in the log_line_prefix setting.  This causes some spewage I'd not seen before
>> on connection received lines as if it is dumping the environment:

> Hmm, I bet it's the recent %.*s patch.

That is in the right place, isn't it.  That would suggest that
get_ps_display() is returning a wrong length on Ray's machine.
It works okay here, but since that's platform-specific code that
hardly proves much.  Ray, what platform is this exactly?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: alvherreDate: 2010-05-27 16:59:17
Subject: Re: command tag logging
Previous:From: Robert HaasDate: 2010-05-27 16:31:48
Subject: Re: Straightforward Synchronous Replication

pgsql-admin by date

Next:From: alvherreDate: 2010-05-27 16:59:17
Subject: Re: command tag logging
Previous:From: Nilesh GovindarajanDate: 2010-05-27 16:32:33
Subject: Re: How to add constraints without validating data.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group