BUG #5026: No buffer space available error. Does any other solution exist other than changing windows paramete

The following bug has been logged online:

Bug reference: 5026
Logged by: Narendra Shah
Email address: narendra(dot)shah(at)elitecore(dot)com
PostgreSQL version: 8.4
Operating system: Windows 2003
Description: No buffer space available error. Does any other solution
exist other than changing windows paramete
Details:

I am using postgres 8.4 and i error of "No buffer space available" when
connecting with the database.

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
iviewdb named database. Other databases are working well and good. After
searching on net i found the limitation is from windows itself. and i have
fixed the error with the following registry hack. But do postgres have any
other solution which is changeble from postgres itself ?

No buffer space available Fix

Editting the registry is not for beginners, if you don't know what you're
doing I suggest you don't try this, basically it's use at your own risk.

Anytime you want to edit the registry it is a good idea to back it up first.
For information on how to backup and restore the registry in all versions of
Windows click here.

If you are using Windows 95/98/Me follow these steps:

First step is to launch the registry editor. To do this go to Start, Run and
type regedit. In the left pane navigate to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP once there,
look for an entry called MaxConnections. If it exists highlight it by
clicking it and then right click it and select modify. Increase the value
(recommended value is to double the current value).

If the MaxConnections entry does not exist you must create it. To do this,
right click in the right pane and choose new from the menu and select String
Value. Give it the name MaxConnections. Then right click it and select
modify and enter a value of 200.

Restart your computer, if all goes well then you fixed the problem, if not,
revert the changes by restoring the registry. (You may have to reboot to
safe mode to do this).

If you are running Windows NT/2000/XP follow these steps: First step is to
launch the registry editor. To do this go to Start, Run and type regedit. In
the left pane navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters once
there, you must create the entry TcpNumConnections. To do this, right click
in the right pane and choose new from the menu and select DWORD Value. Give
it the name TcpNumConnections. Then right click it and select modify and
enter a value of 200.

Restart your computer, if all goes well then you fixed the problem, if not,
revert the changes by restoring the registry. (You may have to reboot to
safe mode to do this).

Regards,
Narendra Shah.
Cyberoam,
Elitecore Technologies Ltd.