From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rolf Lüttecke <rluettecke(at)gcd(dot)de> |
Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] Too many private FDs |
Date: | 1999-12-01 15:34:25 |
Message-ID: | 24495.944062465@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Rolf =?iso-8859-1?Q?L=FCttecke?= <rluettecke(at)gcd(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Hiltibidal | 1999-12-01 16:02:32 | Data Migration |
Previous Message | FM&NB | 1999-12-01 15:25:04 |