Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> I happened to notice that the recently added code to log Bind-message
> >> parameters was printing garbage into my log. On investigation it turned
> >> out to be trying to print an already-pfree'd string. That's
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I happened to notice that the recently added code to log Bind-message
>> parameters was printing garbage into my log. On investigation it turned
>> out to be trying to print an already-pfree'd string. That's fixable,
> Uh, can you sh
At 2006-09-06 18:01:38 -0400, [EMAIL PROTECTED] wrote:
>
> That is, we'd log a Parse or Bind operation if it individually
> exceeded the duration threshold, and not otherwise.
Ok.
> If we've got support for logging the statement text and the parameter
> values at Execute time, isn't logging the p
On Wed, 6 Sep 2006, Tom Lane wrote:
I thought somebody had mentioned that integers were also sent in binary
in the latest driver code? Can't find the archive entry right now though.
Using the fastpath protocol integers and oids are sent as binary. I don't
know if that is related to this
Dave Cramer <[EMAIL PROTECTED]> writes:
> On 6-Sep-06, at 6:01 PM, Tom Lane wrote:
>> * It doesn't log the values of parameters sent in binary mode, which
>> is something that at least JDBC needs.
> AFAIK, we don't need binary mode right away, currently we only send
> bytea parameters in binary
Tom Lane wrote:
> I happened to notice that the recently added code to log Bind-message
> parameters was printing garbage into my log. On investigation it turned
> out to be trying to print an already-pfree'd string. That's fixable,
Uh, can you show me where?
> but having looked at the code clo
On 6-Sep-06, at 6:17 PM, Tom Lane wrote:
Dave Cramer <[EMAIL PROTECTED]> writes:
On 6-Sep-06, at 6:01 PM, Tom Lane wrote:
* It doesn't log the values of parameters sent in binary mode, which
is something that at least JDBC needs.
AFAIK, we don't need binary mode right away, currently we o
On 6-Sep-06, at 6:01 PM, Tom Lane wrote:
I happened to notice that the recently added code to log Bind-message
parameters was printing garbage into my log. On investigation it
turned
out to be trying to print an already-pfree'd string. That's fixable,
but having looked at the code closely,