From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, ashesh(dot)vashi(at)enterprisedb(dot)com, dharmendra(dot)goyal(at)enterprisedb(dot)com, sachin(dot)srivastava(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org, craig(at)postnewspapers(dot)com(dot)au |
Subject: | Re: Minimising windows installer password confusion |
Date: | 2012-06-12 12:53:20 |
Message-ID: | CA+OCxoz+2qNWtzy6OL2p=LScvQDGWa+vzGPS8BGBpTT=MozJ2A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 12, 2012 at 1:49 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
>>
>> I'm not keen on adding additional user accounts - that's a security
>> problem imho. It'll leave the unaware user with multiple accounts on
>> the system, and may cause those that do understand what's going on
>> pain because they'll have to deal with multiple accounts for things
>> like server-side copy.
>
> Oh, I certainly wouldn't do it without *informing* and verifying it
> with the user.
That'll add additional steps for all users, and likely confuse the
novices even more.
>> It also doesn't solve the problem during upgrades, though admittedly
>> that seems to be less common.
>
> Why do you need the account at all during upgrades? Don't you just
> stop the service and replace the binaries?
Because re-running the current installer or running an upgrade should
repair an existing installation as well as doing any upgrades
required.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2012-06-12 12:57:26 | Re: New Postgres committer: Kevin Grittner |
Previous Message | Robert Haas | 2012-06-12 12:52:21 | Re: 9.2 final |