Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 09E5B9ED580 for ; Wed, 7 Dec 2011 09:26:06 -0400 (AST) Received: from mail-gy0-f174.google.com ([209.85.160.174]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RYHVc-0004fP-JD for pgsql-sql@postgresql.org; Wed, 07 Dec 2011 13:26:05 +0000 Received: by ghbz2 with SMTP id z2so477916ghb.19 for ; Wed, 07 Dec 2011 05:25:52 -0800 (PST) Received: by 10.236.186.10 with SMTP id v10mr26635938yhm.54.1323264352181; Wed, 07 Dec 2011 05:25:52 -0800 (PST) Received: from ayaki.localdomain (203-173-33-169.dyn.iinet.net.au. [203.173.33.169]) by mx.google.com with ESMTPS id t3sm5037900anf.0.2011.12.07.05.25.49 (version=SSLv3 cipher=OTHER); Wed, 07 Dec 2011 05:25:51 -0800 (PST) Message-ID: <4EDF695B.1010008@ringerc.id.au> Date: Wed, 07 Dec 2011 21:25:47 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 MIME-Version: 1.0 To: "feng.zhou" CC: pgsql-sql Subject: Re: No response from the backend References: <201112071927138456264@wellintech.com> In-Reply-To: <201112071927138456264@wellintech.com> Content-Type: multipart/alternative; boundary="------------070208020409020305000105" X-Pg-Spam-Score: -0.8 (/) X-Archive-Number: 201112/11 X-Sequence-Number: 36072 This is a multi-part message in MIME format. --------------070208020409020305000105 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 12/07/2011 07:27 PM, feng.zhou wrote: > Hi > There are some questions when using progreSQL8.4.2. I don't sure this > problem is bug.The detail is following: > I make a client program that communicate with progreSQL by ODBC on > Windows7. After running serveral months, this client program is hung > at 00:01 in 2011-11-26 , and become OK after 8 hours.When becoming OK, > client program log message is following: > 2011/11/26 08:38:05.527, : SQL ERROR: GetSelectRowNum: > No response from the backend; > No response from the backend > 2011/11/26 08:38:05.527, : SQL ERROR: GetSelectRowNum: State:42601,Native:26 > 2011/11/26 08:38:05.527, : SQL ERROR: GetSelectRowNum: > Could not send Query(connection dead); > Could not send Query(connection dead) > I don't know how to solve this problem. Someone can explain this > problem cause.Thanks I'd say you had a connectivity drop-out, and it only recovered when your TCP/IP connection timed out. Reduce your TCP/IP timeouts and/or enable keepalives if you have an unreliable network connection between client and server. If that's not the case, then more detail please. Where do the client and server run (same machine?)? How are they connected? etc. -- Craig Ringer --------------070208020409020305000105 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 12/07/2011 07:27 PM, feng.zhou wrote:
Hi
There are some questions when using progreSQL8.4.2. I don't sure this problem is bug.The detail is following:
I make a client program that communicate with  progreSQL by ODBC on Windows7. After running serveral months, this client program is hung at 00:01 in 2011-11-26 , and become OK after 8 hours.When becoming OK, client program log message is following: 
 
2011/11/26 08:38:05.527,  : SQL ERROR: GetSelectRowNum: No response from the backend;
No response from the backend
2011/11/26 08:38:05.527,   : SQL ERROR: GetSelectRowNum: State:42601,Native:26
2011/11/26 08:38:05.527,   : SQL ERROR: GetSelectRowNum: Could not send Query(connection dead);
Could not send Query(connection dead)
 
I don't know how to solve this problem. Someone can explain this problem cause.Thanks

I'd say you had a connectivity drop-out, and it only recovered when your TCP/IP connection timed out. Reduce your TCP/IP timeouts and/or enable keepalives if you have an unreliable network connection between client and server.

If that's not the case, then more detail please. Where do the client and server run (same machine?)? How are they connected? etc.

--
Craig Ringer
--------------070208020409020305000105--