Re: initdb crash - Mailing list pgsql-hackers-win32

From Magnus Hagander
Subject Re: initdb crash
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE34BDCD@algol.sollentuna.se
Whole thread Raw
In response to initdb crash  (nitrogenycs@web.de)
Responses Re: initdb crash
List pgsql-hackers-win32
>hello,
>
>all the permissions u told me are already set (postgres
>subdirs + system
>dirs) and it doesn't work. Is it perhaps possible to make the
>output a bit
>more verbose so i can see which file/path caused the permission denied
>problem? Another idea might be to add an option so that i can
>force it to
>run under an admin user to figure out if that solves the
>problem. I don't
>know how difficult this is though.

Tru running initdb with the "-d" parameter. That should turn on some
debugging output.

//Magnus

pgsql-hackers-win32 by date:

Previous
From: "Gary Doades"
Date:
Subject: Re: initdb crash
Next
From: "Magnus Hagander"
Date:
Subject: Re: initdb crash