Magnus Hagander wrote:
>> Second, once I've successfully built and installed postgres, I run into
>> a bigger problem. When using initdb, I get this error:
>> creating template1 database in c:/Data/postgres30/base/1 ... FATAL:
>> could not create shared memory segment: 5
>> DETAIL: Failed system call was CreateFileMapping(size=1802240,
>> A bit of googling and reading MSDN docs shows that applications that
>> don't run in Session 0 on Vista are not allowed to create shared memory
>> in the Global namespace. Since initdb is invoked from the command line,
>> it runs in Session 1.
> Where did you find that information? I've been specifically looking for
> it, but my searches didn't turn up anything conclusive.
> The latest versions contain a fix for the global namespace code. Dave
> noticed that this caused issues on vista and thus manually reverted the
> patch in the official binary installer. But since we haven't (hadn't)
> yet found documentation as to *why* it was failing, the patch has not
> yet been reverted in the main source tree.
> This is why it's working, probably, and it's not related to how it's built.
> If you want to revert the patch in your local tree, this is the one:
> Specifically, you can reintroduce the old bug (that I think is hat made
> it work on Vista) by removing the +18 in the lowest loop there.
I am getting this error on XP Pro. The buildfarm members run happily
from the scheduler, but when run by hand from the command line they
fail. This is true of both MinGW and MSVC.
This is in *URGENT* need of a fix.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-10-13 23:01:29|
|Subject: Re: WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows |
|Previous:||From: Michael Renner||Date: 2008-10-13 20:49:40|
|Subject: Re: How is random_page_cost=4 ok?|