From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Sachin Srivastava <sachin(dot)srivastava(at)enterprisedb(dot)com>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Dharmendra Goyal <dharmendra(dot)goyal(at)enterprisedb(dot)com> |
Subject: | Re: Minimising windows installer password confusion |
Date: | 2012-06-14 15:59:26 |
Message-ID: | CA+OCxoyrb5PRBrm8JdndgnCq0CRzpR3q0gsvuWX-Ms-G73iRvw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 14, 2012 at 11:43 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
> I'll have a play with it and see if a simple switch to NetworkService
> seems feasible.
OK, I worked up a patch which uses "NT AUTHORITY\NetworkService" as
the service account by default. This doesn't need a password, so
allows us to simply prompt during installation for the superuser
password for the cluster, and not at all during upgrade. If you run
the installer from the command line with "--serviceaccount postgres"
(or some other account name), you get the current behaviour.
I've posted it on our internal ReviewBoard system for the rest of the
team to review and test on various platforms (I've only tried it on XP
so far). Now would be a very good time for people to yelp if they
think this is a bad idea (the only downside I can see if accessing
files for server-side copy etc, but users that want to do that can
install with a non-default account). If we go ahead, we'll include it
in 9.2.
Thanks for the feedback folks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2012-06-14 16:00:31 | Re: libpq compression |
Previous Message | Kohei KaiGai | 2012-06-14 15:43:39 | [v9.3] Row-Level Security |