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 authentica
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 authentica
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 authentica
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 authentica
On Thu, Jul 11, 2013 at 01:43:39PM +, 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 r
Bruce Momjian wrote:
> On Thu, Jul 11, 2013 at 01:43:39PM +, 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 p
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 +, Bruce Momjian wrote:
> > > pg_upgrade: document possible pg_hba.conf options
> > > Previously, pg_upgrade docs recommended using .pgpass if using MD5
> > > authentica
Bruce Momjian writes:
> On Thu, Jul 11, 2013 at 12:13:10PM -0400, Alvaro Herrera wrote:
>> 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 thr
On Thu, Jul 11, 2013 at 05:59:35PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Thu, Jul 11, 2013 at 12:13:10PM -0400, Alvaro Herrera wrote:
> >> Standard operating procedure everyone follos is that you should post the
> >> patch to -hackers first, wait a couple of hours for any possible
Bruce Momjian wrote:
> On Thu, Jul 11, 2013 at 05:59:35PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > On Thu, Jul 11, 2013 at 12:13:10PM -0400, Alvaro Herrera wrote:
> > >> Standard operating procedure everyone follos is that you should post the
> > >> patch to -hackers first, wait a co
On Jul 11, 2013 11:39 PM, "Alvaro Herrera" wrote:
>
> Bruce Momjian wrote:
> > On Thu, Jul 11, 2013 at 05:59:35PM -0400, Tom Lane wrote:
> > > Bruce Momjian writes:
> > > > On Thu, Jul 11, 2013 at 12:13:10PM -0400, Alvaro Herrera wrote:
> > > >> Standard operating procedure everyone follos is tha
pg_dump: Formatting cleanup of new messages
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e852c5df2ded8b076693d0c0632dcbda107be89e
Modified Files
--
src/bin/pg_dump/parallel.c| 44 -
src/bin/pg_dump/pg_backup
pg_dump: Formatting cleanup of new messages
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/7484f89daa33477e0027a86ae772f44fa99224ed
Modified Files
--
src/bin/pg_dump/parallel.c| 44 -
src/bin/pg_dump/pg
13 matches
Mail list logo
