Re: EnterpriseDB OneClick Installer Broken

On Thu, Jul 2, 2009 at 6:26 PM, Joshua Kramer<josh(at)globalherald(dot)net> wrote:
>
> Ok, I know this isn't strictly an 'advocacy' issue, but it is something that
> could reflect badly upon PG.
>
> In the EnterpriseDB OneClick Windows installer, the password handling does
> not work.  On the initial password entry, where it says 'if you do not enter
> a password, one will be created for you'... if you don't enter a password,
> it complains that you didn't enter a password.  I deleted the postgres
> Windows account from the previous 8.3 install.

Please read the message more carefully before complaining that we're
bringing PostgreSQL into disrepute - that is *not* what it says.

What it actually does say is:

===
Please provide a password for the database superuser 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'.
===

> Also, after installation, when I try to connect to my new installation with
> pgAdminIII, I can't connect... it never sets the 'postgresql' user password
> in the database.  Or if it does, it doesn't tell me what that password is.

There is no 'postgresql' user, it's 'postgres'. The installer uses
initdb's --pwfile option to ensure it gets set to whatever you entered
previously. Between the the hundreds of test run installs we've done,
and the hundreds of thousands of copies people have downloaded, I'm
confident a major bug such as you describe would have been reported
already.

>  It's not the same as the password entered in the step above. To connect, I
> have to edit pg_hba.conf, set localhost auth to 'trust', change the
> password, and then reset localhost auth to 'md5'.

It's not beyond the realms of possibility that you have encountered a
corner-case bug though. Any non-alphanumeric characters in the
password you're using? Also of course, the normal questions about
whether your initial password entry might have been affected by
inadvertent use of caps lock or num lock must be asked.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com