Hi Lennnin,
Thanks a lot for providing your kind help. But after tweaking registry, yet
problem not solved. On yesterday evening when i check again. Same problem
occured, what i have done is i have queried one table. Then after Database
again giving me the same error. Requesting you to please pro
--- On Tue, 9/1/09, Narendra Shah wrote:
From: Narendra Shah
Subject: Re: [GENERAL] No buffer space available
To: pgsql-general@postgresql.org
Date: Tuesday, September 1, 2009, 11:53 AM
I am using machine which is exceeding more than 100 connection from my
application(iview-syslog server
I am using machine which is exceeding more than 100 connection from my
application(iview-syslog server) to postgres. I have updated configuration
for postgres in postgres.conf for max connection. But then also it is giving
me the error as No buffer space available. And it is happening with only
iv
"Nik" <[EMAIL PROTECTED]> writes:
> Now I wonder why is it that I started getting WSANOBUFS errors from
> Windows Socket System if this same setup with the same machines has
> been operational for over a year? The query size did not change and
> the number of connections to the server did not chan
On Mar 6, 2:20 pm, [EMAIL PROTECTED] ("Andrej Ricnik-Bay")
wrote:
> On 3/7/07, andyk <[EMAIL PROTECTED]> wrote:
>
> > 1) try to use client software, which is not depends on libpq,
> > or
> > 2) divide your query into smaller parts,
> > or
> > 3) use software which parses long queries, separates the
On Wed, Mar 07, 2007 at 07:46:16AM +0100, Martijn van Oosterhout wrote:
> On Tue, Mar 06, 2007 at 08:38:22PM +0200, andyk wrote:
> >This error is returned by libpq, as a reaction on WSANOBUFS error
> > from Windows Socket System. This means, applications tries to send much
> > data, and system
On Tue, Mar 06, 2007 at 08:38:22PM +0200, andyk wrote:
>This error is returned by libpq, as a reaction on WSANOBUFS error
> from Windows Socket System. This means, applications tries to send much
> data, and system can't do it the same quickly. Possible, libpq should
> handle this error more ca
On 3/7/07, andyk <[EMAIL PROTECTED]> wrote:
1) try to use client software, which is not depends on libpq,
or
2) divide your query into smaller parts,
or
3) use software which parses long queries, separates them into single
SQL commands and then executes this commands one by one.
4) use Postgres
Nik wrote:
I have an SQL file with a set of about 3000 insert statements. This
file is executed twice from a remote client machine running Windows
XP. The first time it is executed against a Windows 2003 Server
running PostgreSQL 8.0. The second time it is executed against a
Windows 2003 Server r
