Steve McWilliams wrote:
>Nevermind, I found out what this was. Turned out that the customer
>machine in question had particularly heavy security settings and so the
>enetaware account did not have permission to write into the directory
>where it was trying to create PGDATA. Once I widened the settings on the
>parent directory then it worked fine. Kind of odd that inidb.exe just
>fails silently when this is the case however.
>
>
>
Very odd, since initdb calls chmod to fix the directory permissions, if
it already exists, and creates it with those same permissions if it
isn't (in both cases the permissions are 0700 ). If that isn't enough on
Windows, perhaps someone can tell us what is.
cheers
andrew
