I have log_min_error_statement set to 'info'
But, right you are. I put Wireshark on the job and yes, I'm producing a
mangled query, which the postgres driver for my application never
On 11/28/2010 8:58 AM, Tom Lane wrote:
> Stuart Kendrick<skendric(at)fhcrc(dot)org> writes:
>> Usually, I see the SQL statements which my application emits appear in
> You have not shown us your log-related settings, but it looks like the
> log entries you're mentioning here are for duration logging, which is
> only done on successful completion.
>> But when my application emits this statement, postgres logs neither the
>> SQL query nor an error message ... just the usual connect/disconnect
>> stuff. And the result set, of course, is empty.
> Perhaps you have log_min_error_statement set to a funny value? But I'd
> suspect there is some logic error on the client side such that you're
> never actually submitting the statement.
> regards, tom lane
In response to
pgsql-novice by date
|Next:||From: rchowdhury||Date: 2010-11-30 17:17:39|
|Subject: Use for loop in stored procedure to join query results|
|Previous:||From: Stuart Kendrick||Date: 2010-11-28 19:38:25|
|Subject: Re: log statements span multiple lines|