Обсуждение: No response from the backend
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
2011-12-07
feng.zhou
On 12/07/2011 07:27 PM, feng.zhou wrote:
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
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
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
Thanks for your answer.
The client and server run on the same machine(Windows7). They are connected by ODBC.The client accesses server by call ODBC API.Connection and query timeout don't be set in the client.
2011-12-08
feng.zhou
发件人： Craig Ringer
发送时间： 2011-12-07 21:03:46
收件人： feng.zhou
抄送： pgsql-sql
主题： Re: [SQL] No response from the backend
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
On 12/08/2011 09:38 AM, feng.zhou wrote:
Since client and server are on the same host, it's unlikely to be network connectivity. Check the server logs.
--
Craig Ringer
@font-face { font-family: 宋体; } @font-face { font-family: Verdana; } @font-face { font-family: @宋体; } @page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; layout-grid: 15.6pt; } P.MsoNormal { TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt } LI.MsoNormal { TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt } DIV.MsoNormal { TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: purple; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline } SPAN.EmailStyle17 { FONT-STYLE: normal; FONT-FAMILY: Verdana; COLOR: windowtext; FONT-WEIGHT: normal; TEXT-DECORATION: none; mso-style-type: personal-compose } DIV.Section1 { page: Section1 } UNKNOWN { FONT-SIZE: 10pt } Thanks for your answer.The client and server run on the same machine(Windows7). They are connected by ODBC.The client accesses server by call ODBC API.Connection and query timeout don't be set in the client.
Since client and server are on the same host, it's unlikely to be network connectivity. Check the server logs.
--
Craig Ringer
Since client and server are on the same host, it's unlikely to be network connectivity. Check the server logs.
--
Craig Ringer
Thanks, I will try it
2011-12-08
feng.zhou
发件人： Craig Ringer
发送时间： 2011-12-08 11:49:33
收件人： feng.zhou
抄送： pgsql-sql
主题： Re: [SQL] No response from the backend
On 12/08/2011 09:38 AM, feng.zhou wrote:
Thanks for your answer.
The client and server run on the same machine(Windows7). They are connected by ODBC.The client accesses server by call ODBC API.Connection and query timeout don't be set in the client.
Since client and server are on the same host, it's unlikely to be network connectivity. Check the server logs.
--
Craig Ringer