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

Re: BUG #5475: Problem during Instalation

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Joel Henrique <joel(at)cefet-al(dot)br>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5475: Problem during Instalation
Date: 2010-06-09 14:57:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Wed, Jun 9, 2010 at 10:52 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Wed, Jun 9, 2010 at 3:50 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Wed, Jun 9, 2010 at 6:09 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>> Please provide a password for the database superuser (${superaccount})
>>> and service account (${serviceaccount}). If the service account
>>> already exists in Windows, you must enter the current password for the
>>> account. If the account does not exist, it will be created when you
>>> click 'Next'.
>> I think that's REALLY confusing.  It seems to me that asking for a
>> password which might be used either to log into an existing account or
>> to set the password for an account that's about to be created is not
>> very user-friendly at all.  And we get questions about it here
>> regularly.  Why not:
>> If (account exists)
>>  prompt user to log into account
>> else
>>  tell user account will be created, ask for account pw
>> prompt user for db superuser pw
> Because without additional text, the user still doesn't know that
> they're also setting the superuser password for the cluster.

I'm suggesting that you prompt for that separately, as shown in the
above pseudocode.  It seems to me that conflating the postgres user
account password with the database superuser password is confusing...
IJWH, of course.

Robert Haas
The Enterprise Postgres Company

In response to


pgsql-bugs by date

Next:From: Dave PageDate: 2010-06-09 14:58:55
Subject: Re: BUG #5475: Problem during Instalation
Previous:From: Robert HaasDate: 2010-06-09 14:53:03
Subject: Re: Bad optimizer data for xml (WAS: xml data type implications of no =)

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