Re: win32 pgsql not installable - Mailing list pgsql-hackers-win32

From Magnus Hagander
Subject Re: win32 pgsql not installable
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE4569B2@algol.sollentuna.se
Whole thread Raw
In response to win32 pgsql not installable  (Andreas Pflug <pgadmin@pse-consulting.de>)
Responses Re: win32 pgsql not installable
List pgsql-hackers-win32
> > >I know I'm going to go on some people's nerves, but it's necessary.
> > >
> > >With the current "run-as-non-admin" restriction the
> windows installer
> > >doesn't work, and it will probably be ridiculously
> difficult to make
> > >it work unless this restriction is redesigned.
> >
> > Not commenting on the other parts, but *huh*? The windows installer
> > works just fine. It does require that you manually set up a
> non-admin
> > account, but it certainly *works*...
>
> And you have to tell the system that user can start a service.

Yes and no.
The *service account* needs permissions to "Log On as a Service". It
specifically does *NOT* need permission to start/stop services, or any
other admin privileges.
The *install account* needs permissions to install files, *install*
services and start/stop services.

These accounts should always be different. The install account is the
administrator account, or whatever other accuont you use to setup your
system. The service account would typicall be called "postgres".


//Magnus


pgsql-hackers-win32 by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: initdb crashing, signal 5, etc
Next
From: "Magnus Hagander"
Date:
Subject: Re: initdb problem in Korean OS.