Thread: BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation
BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation
From
"gouthamj"
Date:
The following bug has been logged online: Bug reference: 5450 Logged by: gouthamj Email address: jgowtham@gmail.com PostgreSQL version: 8.1.5 Operating system: Window xp(sp2) Description: system lacked sufficient buffer space, or because a queue was full, could not perform the operation Details: 2010-04-20 00:53:29 LOG: unexpected EOF on client connection 2010-04-20 00:55:47 LOG: could not receive data from client: the system lacked sufficient buffer space, or because a queue was full, could not perform the operation on a socket.
Re: BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation
From
Takahiro Itagaki
Date:
"gouthamj" <jgowtham@gmail.com> wrote: > PostgreSQL version: 8.1.5 > Operating system: Window xp(sp2) Sorry, PostgreSQL 8.1 on Windows is no longer supported. Please upgrade to 8.2 or newer versions, and test your sequence again. BTW, your message comes from WSAENOBUFS (10055). The error could be raised by various reasons. We need what you did when you receive the message to research your problem. > Description: system lacked sufficient buffer space, or because a > queue was full, could not perform the operation > Details: > > 2010-04-20 00:53:29 LOG: unexpected EOF on client connection > 2010-04-20 00:55:47 LOG: could not receive data from client: the system > lacked sufficient buffer space, or because a queue was full, could not > perform the operation on a socket. Regards, --- Takahiro Itagaki NTT Open Source Software Center
Re: BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation
From
goutham jalakam
Date:
Hi Takahiro san, Thanks a lot for mail. Our application has to take backup aroung 200GB or more data based on Database. Physical files in the local system will be uploaded to NAS raid server based on Database records. for each and every database record associated files wil be available. So, more than 300000 times database queries and updates to DB and around 600000 files to be uploaded to NAS. Regards Goutham J On Thu, May 6, 2010 at 12:44 AM, Takahiro Itagaki < itagaki.takahiro@oss.ntt.co.jp> wrote: > > "gouthamj" <jgowtham@gmail.com> wrote: > > > PostgreSQL version: 8.1.5 > > Operating system: Window xp(sp2) > > Sorry, PostgreSQL 8.1 on Windows is no longer supported. > Please upgrade to 8.2 or newer versions, and test your sequence again. > > BTW, your message comes from WSAENOBUFS (10055). The error could be > raised by various reasons. We need what you did when you receive > the message to research your problem. > > > Description: system lacked sufficient buffer space, or because a > > queue was full, could not perform the operation > > Details: > > > > 2010-04-20 00:53:29 LOG: unexpected EOF on client connection > > 2010-04-20 00:55:47 LOG: could not receive data from client: the system > > lacked sufficient buffer space, or because a queue was full, could not > > perform the operation on a socket. > > Regards, > --- > Takahiro Itagaki > NTT Open Source Software Center > > >
Re: BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation
From
Takahiro Itagaki
Date:
goutham jalakam <jgowtham@gmail.com> wrote: > Our application has to take backup aroung 200GB or more data based on > Database. > > Physical files in the local system will be uploaded to NAS raid server based > on Database records. > for each and every database record associated files wil be available. > So, more than 300000 times database queries and updates to DB and around > 600000 files to be uploaded to NAS. Have you check KB196271 already? It might be an issue in Windows. http://support.microsoft.com/kb/196271/en > > > PostgreSQL version: 8.1.5 > > > Operating system: Window xp(sp2) > > > > BTW, your message comes from WSAENOBUFS (10055). The error could be > > raised by various reasons. We need what you did when you receive > > the message to research your problem. Regards, --- Takahiro Itagaki NTT Open Source Software Center