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 KAA64846
	for <pgsql-interfaces@postgreSQL.org>;
	Wed, 1 Dec 1999 10:35:36 -0500 (EST)
	(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 KAA24497;
	Wed, 1 Dec 1999 10:34:25 -0500 (EST)
To: Rolf =?iso-8859-1?Q?L=FCttecke?= <rluettecke@gcd.de>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Too many private FDs 
In-reply-to: Your message of Wed, 01 Dec 1999 09:42:13 +0100
	<3844DF65.FF29CA5A@gcd.de>
Date: Wed, 01 Dec 1999 10:34:25 -0500
Message-ID: <24495.944062465@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Rolf =?iso-8859-1?Q?L=FCttecke?= <rluettecke@gcd.de> writes:
> is anyone able to explain the following error-message extracted from
> the "server.log"?

> -- ERROR:  AllocateFile: too many private FDs demanded

Do you use password verification for any of your clients?

There is a file descriptor leak in the 6.5.* postmaster that is
triggered when an invalid user name is presented to the password
check routine.  Add a FreeFile() call to the bottom of the check
routine, like this:

*** src/backend/libpq/password.c.orig	Tue May 25 12:09:00 1999
--- src/backend/libpq/password.c	Wed Dec  1 10:30:46 1999
***************
*** 90,95 ****
--- 90,97 ----
  			return STATUS_ERROR;
  		}
  	}
+ 
+ 	FreeFile(pw_file);
  
  	snprintf(PQerrormsg, ERROR_MSG_LENGTH,
  			 "verify_password: user '%s' not found in password file.\n",


This is fixed in current sources and will be fixed in 6.5.4, if
there is another 6.5.* release...

If you *don't* use this style of authentication then we need to
look harder :-(

			regards, tom lane