Re: Win 32 'could not attach to proper memory at fixed address'

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Bryan Roberts" <bryan(at)aotea(dot)co(dot)nz>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Win 32 'could not attach to proper memory at fixed address'
Date: 2004-12-13 16:20:36
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE476383@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Running RC1 on Windows 2003 Server I get the following:
>
> 2004-12-13 13:01:11 FATAL: could not attach to proper memory
> at fixed address:
> shmget(key=5432001, addr=00DB0000) failed: Invalid argument
> 2004-12-13 13:01:11 FATAL: could not attach to proper memory
> at fixed address:
> shmget(key=5432001, addr=00DB0000) failed: Invalid argument
> 2004-12-13 13:01:11 LOG: background writer process (PID
> 3548) exited with exit code 0
> 2004-12-13 13:01:11 LOG: terminating any other active server
> processes
> 2004-12-13 13:01:11 LOG: all server processes terminated;
> reinitializing
>
> I noticed that there are a couple of references to this on
> the mailing list however the 'Invalid argument' part of the
> message appears to be different.
>
> The problem can be worked around (if you are running locally)
> by changing the postgresql.conf from:
> listen_addresses = '*'
> to:
> listen_addresses = '127.0.0.1'

You're saying this only happens if listen_addresses='*'? *very*
interesting.

Are you running this off the console or through a RDP session?

//Magnus

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2004-12-13 17:10:09 Re: postgresql-8.0.0 beta5 & postgresql-7.4.6 can't compile successfully
Previous Message Oliver Jowett 2004-12-13 13:26:52 Re: [BUGS] BUG #1347: Bulk Import stopps after a while (