From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: pg_upgrade: document possible pg_hba.conf options |
Date: | 2013-07-11 21:48:55 |
Message-ID: | 20130711214855.GA12667@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Thu, Jul 11, 2013 at 12:13:10PM -0400, Alvaro Herrera wrote:
> 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.
I don't think we need that formality with a doc patch. I don't see
others doing that.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-07-11 21:59:35 | Re: pgsql: pg_upgrade: document possible pg_hba.conf options |
Previous Message | Alvaro Herrera | 2013-07-11 16:13:10 | Re: pgsql: pg_upgrade: document possible pg_hba.conf options |