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

From: Bryan Roberts <bryan(at)aotea(dot)co(dot)nz>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Win 32 'could not attach to proper memory at fixed address'
Date: 2004-12-13 00:28:18
Message-ID: 1102897698.41bce222423d3@mail.thinktomorrow.com
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'

Thanks,
Bryan Roberts

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2004-12-13 07:20:18 BUG #1347: Bulk Import stopps after a while ( 8.0.0. RC1)
Previous Message Josh Berkus 2004-12-12 20:17:47 Re: concat fails 'sometimes' on empty colums in select