| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: initdb check_need_password fix |
| Date: | 2012-06-28 23:24:01 |
| Message-ID: | CA+TgmoZAdAxR4b+9rkazPmxTPkK=1szGhVkodEKG9ancZYS9Ww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 28, 2012 at 3:48 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> If you run initdb -A md5, you get an error
>
> initdb: must specify a password for the superuser to enable md5 authentication
>
> In 9.2, when you run something like initdb --auth-local=peer
> --auth-host=md5, you still get that error, which I think is a mistake.
> The error should only be shown if both authentication choices are
> password-like. Hence I propose the attached patch.
Looks right to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-28 23:48:55 | Re: We probably need autovacuum_max_wraparound_workers |
| Previous Message | Jan Urbański | 2012-06-28 22:36:47 | Re: plpython issue with Win64 (PG 9.2) |