Minimising windows installer password confusion

From: Dave Page <dpage(at)pgadmin(dot)org>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, 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: Minimising windows installer password confusion
Date: 2012-06-12 12:08:41
Message-ID: CA+OCxowqu=XBY_X2JfngzQtG2G8gQvmOc4paiT_s9anP0KGC3Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Probably the most common issue we see from Windows users of PostgreSQL
is confusion over the passwords the installer asks for during
installation and upgrade. I'd like to try to reduce that, but am
struggling to come up with clear, simple wording.

Some background: By default the installer will use 'postgres' for both
the service (OS) account, and the database superuser account. It will
use the same password for both (though, users have complete control at
the command line if they want it, which is why the account names are
shown in the installer). Unlike *nix installations, the service
account must have a password, which is required during both
installation and upgrade to configure the PostgreSQL service. We
therefore ask for the password during both installation and upgrade.
If the user account exists (which can happen if there has previously
been an installation of Postgres on the system), the user must specify
the existing password for the account during installation (and of
course, during all upgrades). This is where users normally get stuck,
as they've forgotten the password they set in the past.

Attached are some screenshots of the current installation and upgrade
steps in question, and the password incorrect message box. The
suggested new text for the steps that I've come up with is below. I'd
welcome suggestions or improvements to help reduce pgsql-bugs traffic!

Thanks.

Installation step:

*******************************
Please provide a password for the database superuser (postgres) and
service account (postgres). 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'.

Password [ ]
Retype password [ ]

If the service account already exists on your computer and you don't
know the password, you can reset it using the Computer Management tool
in the Administrative Tools section of the Control Panel. You may need
update any other services that are using this account with the new
password.

Note that this password is not related to any used on the PostgreSQL
or EnterpriseDB websites.
*******************************

Upgrade step:

*******************************
Please provide the password for the service account (postgres).

Password [ ]
Retype password [ ]

If you don't know the password, you can reset it using the Computer
Management tool in the Administrative Tools section of the Control
Panel. You may need update any other services that are using this
account with the new password.

Note that this password is not related to any used on the PostgreSQL
or EnterpriseDB websites.
*******************************

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment Content-Type Size
image/png 54.4 KB
image/png 43.6 KB
image/png 14.3 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2012-06-12 12:26:18 Re: Minimising windows installer password confusion
Previous Message Kyotaro HORIGUCHI 2012-06-12 11:43:07 Re: Skip checkpoint on promoting from streaming replication