Skip site navigation (1) Skip section navigation (2)

Re: Minimising windows installer password confusion

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: (view raw or whole 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

Dave Page
Twitter: @pgsnake

EnterpriseDB UK:
The Enterprise PostgreSQL Company

In response to


pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2012-06-12 12:57:26
Subject: Re: New Postgres committer: Kevin Grittner
Previous:From: Robert HaasDate: 2012-06-12 12:52:21
Subject: Re: 9.2 final

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group