Re: Win 32 'could not attach to proper memory at fixed address'
| От | Magnus Hagander |
|---|---|
| Тема | Re: Win 32 'could not attach to proper memory at fixed address' |
| Дата | |
| Msg-id | 6BCB9D8A16AC4241919521715F4D8BCE476383@algol.sollentuna.se обсуждение исходный текст |
| Ответ на | Win 32 'could not attach to proper memory at fixed address' (Bryan Roberts <bryan@aotea.co.nz>) |
| Ответы |
Re: Win 32 'could not attach to proper memory at fixed address'
Re: Win 32 'could not attach to proper memory at fixed address' |
| Список | pgsql-bugs |
> Running RC1 on Windows 2003 Server I get the following:=20 >=20 > 2004-12-13 13:01:11 FATAL: could not attach to proper memory=20 > at fixed address: > shmget(key=3D5432001, addr=3D00DB0000) failed: Invalid argument > 2004-12-13 13:01:11 FATAL: could not attach to proper memory=20 > at fixed address: > shmget(key=3D5432001, addr=3D00DB0000) failed: Invalid argument > 2004-12-13 13:01:11 LOG: background writer process (PID=20 > 3548) exited with exit code 0 > 2004-12-13 13:01:11 LOG: terminating any other active server=20 > processes > 2004-12-13 13:01:11 LOG: all server processes terminated;=20 > reinitializing >=20 > I noticed that there are a couple of references to this on=20 > the mailing list however the 'Invalid argument' part of the=20 > message appears to be different. >=20 > The problem can be worked around (if you are running locally)=20 > by changing the postgresql.conf from: > listen_addresses =3D '*' > to: > listen_addresses =3D '127.0.0.1' You're saying this only happens if listen_addresses=3D'*'? *very* interesting. Are you running this off the console or through a RDP session? //Magnus
В списке pgsql-bugs по дате отправления: