From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rolf Lüttecke <rluettecke@gcd.de>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Too many private FDs
Date: Wed, 01 Dec 1999 10:34:25 -0500
Message-ID: <24495.944062465@sss.pgh.pa.us> (raw)
In-Reply-To: <3844DF65.FF29CA5A@gcd.de>
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:
inline patch 1: src/backend/libpq/password.c (+2/-0 lines) download inline-1.patch*** 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, rluettecke@gcd.de
Subject: Re: [INTERFACES] Too many private FDs
In-Reply-To: <24495.944062465@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox