Skip site navigation (1) Skip section navigation (2)

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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <mha(at)sollentuna(dot)net>,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 18:40:14
Message-ID: 200412131840.iBDIeE701624@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > 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.
> 
> I see no proof of that at all in this bug report.  The postmaster has
> evidently managed to create the segment, so the address per se is not
> the problem.

Really?  You do realize we just choose a fixed address on Win32, right?

I will remove the item and see how it plays out though.

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

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-12-13 18:51:30
Subject: Re: Win 32 'could not attach to proper memory at fixed address'
Previous:From: Tom LaneDate: 2004-12-13 18:33:11
Subject: Re: Win 32 'could not attach to proper memory at fixed address'

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group