Re: "1-Click" installer problems

This is of interest to me, because something similar happens on the
Mac (with the one-click installer).

The data directory is placed in a file that user 'postgres' has
permission on. Of course, this is a new user, created by postgres,
but what it ends up meaning is that I run all my postgres files under
root instead of in my user directory.

Now, I know that is stupid, cludgy, and probably un-American, but it
was the simplest work-around I came up with.

I wonder if the problems arise because user 'postgres' is being
created on the Windows machine and no one expects him, knows he's
there, or has ever met him?

John

On Apr 1, 2010, at 9:09 AM, Thomas Kellerer wrote:

> Nikhil G. Daddikar, 01.04.2010 08:04:
>>
>> In about 30 seconds I found the following unanswered threads
>> relating to
>> installation on Windows Vista. If anybody is interested I can find
>> more.
>
> The problem with this kind of statistics is that you will only find
> people who complain, you'll never find people who do not complain
> because they have no problems. Actually that's true for all internet
> forums or mailing lists: you'll seldomly find people posting
> something like "Hey everything works fine, I had no problems".
>
> All the posts seem to share the same root cause: the data directory
> has been put into "c:\Program Files" but a regular user does not
> have write permissions on that directory. As the installer is
> usually run with Administrator rights, the directory can be created
> but the service (or initdb) runs under a normal user account that
> cannot write to that directory because.
>
> I do not like the installer's suggestion to put the data directory
> into c:\Program Files either, I think this should default to %APPDATA
> % instead of %ProgramFile%. I bet half of the problems would go away
> if the installer refused to put the data directory into c:\Program
> Files.
>
> Given the fact that Microsoft finally tries to enforce people not to
> work as Administrators makes this even more important.
>
> My suggestion is to try to use a different data directory when
> installing Postgres and make sure that the postgres service account
> is allowed to read and write that directory.
>
> Personally I switched to using the ZIP packages completely because
> it is so much easer (unzip, initdb, pg_ctl -register, done)
>
> Thomas
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general