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

Added to TODO for Win32:

        o Allow the shared memory address to be configured via GUC

This is something we knew might be required and now I think it is
required.  Using a fixed address was always pretty crazy.

---------------------------------------------------------------------------

Magnus Hagander wrote:
> > 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073