Kevin,
On Wed, Nov 13, 2002 at 10:41:06AM -0700, Kevin Wong wrote:
> Why is a "postgres" user different than a "Cygwin installer user"
> in this context?
>
> The best theory I can come up with is file/directory ownership. That
> is, an XP user simply created and named as "postgres" user won't have
> ownership of the postgres files/directories. Therefore, it will have
> countless problems when trying to execute. Nor does SYSTEM work, even
> though it should theoretically have root-like access to the
> filesystem.
>
> I've even attemped recursive "chown"'s of the various directories to
> the postgres user. Perhaps I simply missed a few files/directories,
> and therefore postgres couldn't read or write to something it needed
> to. I don't know.
>
> [snip]
>
> I would really like to determine whether or not a "postgres" user
> can be used. If not, then we will go with your "Cygwin installer
> user" suggestion.
>
> Gotcha. Again, I'll give it another shot. Of course, if the
> "postgres" user IS the "Cygwin installer user" then there'd definitely
> be no problem. Though, I find it highly unlikely that this would be
> the case in most instances.
My suggestion is to login as "postgres" and then run initdb. By
"login", I mean at the Windows login dialog or use ssh to simulate su.
Hopefully, running initdb as "postgres" will solve your permissions
problem.
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6