| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | pgsql-advocacy(at)postgresql(dot)org |
| Subject: | Re: EnterpriseDB OneClick Installer Broken |
| Date: | 2009-07-06 07:43:19 |
| Message-ID: | 937d27e10907060043g5d8e0f2eo390be6bf4d814dbb@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Thu, Jul 2, 2009 at 7:49 PM, Thomas Kellerer<spam_eater(at)gmx(dot)net> wrote:
> In my case it *was* the password I entered for the service account, which I
> found a bit confusing.
>
> I'm not sure whether that dialog box actually mentioned that the same
> password was used for the postgres super user and the service account.
It does:
Please provide a password for the database superuser and service
account (postgres)....
> In my case the service account already existed, I don't know if that makes a
> difference
On Windows, it means you must reuse the current password. You can of
course, update the superuser password later in psql or pgAdmin. On
Linux & Mac we don't set a service account password so it'll just use
the password specified for the superuser regardless.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Kramer | 2009-07-06 14:58:50 | Re: EnterpriseDB OneClick Installer Broken |
| Previous Message | Dave Page | 2009-07-04 23:54:23 | Re: EnterpriseDB OneClick Installer Broken |