Re: pgsql: pg_upgrade: document possible pg_hba.conf options
От | Alvaro Herrera |
---|---|
Тема | Re: pgsql: pg_upgrade: document possible pg_hba.conf options |
Дата | |
Msg-id | 20130711161310.GA29206@eldon.alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: pgsql: pg_upgrade: document possible pg_hba.conf options (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: pgsql: pg_upgrade: document possible pg_hba.conf
options
|
Список | pgsql-committers |
Bruce Momjian wrote: > On Thu, Jul 11, 2013 at 01:43:39PM +0000, Bruce Momjian wrote: > > pg_upgrade: document possible pg_hba.conf options > > Previously, pg_upgrade docs recommended using .pgpass if using MD5 > > authentication to avoid being prompted for a password. Turns out pg_ctl > > never prompts for a password, so MD5 requires .pgpass --- document that. > > Also recommend 'peer' for authentication too. > > Backpatch back to 9.1. > > When I make a commit like this, should I send an email to hackers that > basically duplicates this information? I assume no. Standard operating procedure everyone follos is that you should post the patch to -hackers first, wait a couple of hours for any possible input, push the commit, then reply to the original -hackers thread stating you have committed it. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-committers по дате отправления: