Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA35016
	for <pgsql-interfaces@postgreSQL.org>;
	Tue, 27 Jul 1999 10:31:36 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA07020;
	Tue, 27 Jul 1999 10:28:33 -0400 (EDT)
To: stuart@comodo.net
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] SOMAXCONN, MaxBackendID and Postgres 
In-reply-to: Your message of Tue, 27 Jul 1999 10:45:55 +0000
	<99072710572500.00398@kevin>
Date: Tue, 27 Jul 1999 10:28:33 -0400
Message-ID: <7018.933085713@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

StOo <stuart@comodo.net> writes:
> O/S  S.u.s.e linux 6.0
> kernel 2.0.36
> postgres 6-4-2 

> I'm trying to increase the maximum number of connections  on the operating
> system which invovles altering the SOMAXCONN and patching certain
> files.

Changing the max number of backends in 6.4.* is pretty painful.  I'd
suggest updating to 6.5.1 --- you can set the max to as high as 1024
without even recompiling.

Whether your kernel will support that many is another question.  Aside
from the connections themselves, you need adequate swap space, file
table slots, etc to support that many processes.  You will also need
larger-than-typical limits on the size of the shared memory block and
on the max number of semaphores.

			regards, tom lane