Re: debugging SQL statements

Поиск
Список
Период
Сортировка
От Stuart Kendrick
Тема Re: debugging SQL statements
Дата
Msg-id 4CF2B04C.3090103@fhcrc.org
обсуждение исходный текст
Ответ на Re: debugging SQL statements  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Attempting backup  (Mick <mickg01@verizon.net>)
Список pgsql-novice
Hi Tom,

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
actually submits.

Thank you,

--sk

On 11/28/2010 8:58 AM, Tom Lane wrote:
> Stuart Kendrick<skendric@fhcrc.org>  writes:
>> Usually, I see the SQL statements which my application emits appear in
>> syslog:
>
> 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

В списке pgsql-novice по дате отправления:

Предыдущее
От: Stuart Kendrick
Дата:
Сообщение: Re: log statements span multiple lines
Следующее
От: rchowdhury
Дата:
Сообщение: Use for loop in stored procedure to join query results