Re: pgsql: pg_upgrade: document possible pg_hba.conf options - Mailing list pgsql-committers

From Alvaro Herrera
Subject Re: pgsql: pg_upgrade: document possible pg_hba.conf options
Date
Msg-id 20130711161310.GA29206@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: pgsql: pg_upgrade: document possible pg_hba.conf options  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pgsql: pg_upgrade: document possible pg_hba.conf options  (Bruce Momjian <bruce@momjian.us>)
List 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 by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pgsql: pg_upgrade: document possible pg_hba.conf options
Next
From: Bruce Momjian
Date:
Subject: Re: pgsql: pg_upgrade: document possible pg_hba.conf options