diff options
| author | Marc G. Fournier <scrappy@hub.org> | 1998-03-15 08:15:46 +0000 |
|---|---|---|
| committer | Marc G. Fournier <scrappy@hub.org> | 1998-03-15 08:15:46 +0000 |
| commit | bb7f173c0c07db2973e4b35286560ca8cc01d3a1 (patch) | |
| tree | 78ca6a3a86c6f0521e5da9a7bccb73bbd65524e4 /src/backend/regex/engine.c | |
| parent | e4135ad17e51fa4e5b884c76cff8608e219fa2c7 (diff) | |
| download | postgresql-bb7f173c0c07db2973e4b35286560ca8cc01d3a1.tar.gz postgresql-bb7f173c0c07db2973e4b35286560ca8cc01d3a1.zip | |
Reply-To: Jordi MacDonald <jordi@spartanmedia.com>
There is an error in the configure script when using
--with-pgport= that will cause the compiled version of
PostgreSQL to no longer allow connections to the
new port and to treat shared memory improperly.
What happens is that if the port is changed, the configure
script defines DEF_PGPORT as "", which atoi() will return
as 0, which makes the IPC_KEY value 0. This then causes
semaphores to be allocated, but never released. Postgres
eventually returns from semget() with
"no space left on device". The source of this error could
easily be overlooked in version 6.3 since it is possible
to connect via UNIX domain sockets, and having DEF_PGPORT
defined as "0" would not be noticed until TCP was used.
Diffstat (limited to 'src/backend/regex/engine.c')
0 files changed, 0 insertions, 0 deletions