Re: BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: goutham jalakam <jgowtham(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation
Date: 2010-05-10 03:14:15
Message-ID: 20100510121415.9C45.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


goutham jalakam <jgowtham(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Takahiro Itagaki 2010-05-10 06:34:19 Re: "SET search_path" clause ignored during function creation
Previous Message Greg Stark 2010-05-10 01:02:39 Re: bool: symbol name collision