Re: [HACKERS] replication and pg_hba.conf

2011-01-17 Thread Robert Haas
On Jan 17, 2011, at 1:44 AM, Heikki Linnakangas wrote: > But I wonder if we should add lines in the default pg_hba.conf to "trust" > replication connections from loopback, like we do for normal connections? Seems sorta pointless. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] replication and pg_hba.conf

2011-01-16 Thread Magnus Hagander
On Mon, Jan 17, 2011 at 07:44, Heikki Linnakangas wrote: > On 16.01.2011 22:55, Josh Berkus wrote: >> >>> In 9.0, we specifically require using "replication" as database name >>> to start a replication session. In 9.1 we will have the REPLICATION >>> attribute to a role - should we change it so th

Re: [HACKERS] replication and pg_hba.conf

2011-01-16 Thread Heikki Linnakangas
On 16.01.2011 22:55, Josh Berkus wrote: In 9.0, we specifically require using "replication" as database name to start a replication session. In 9.1 we will have the REPLICATION attribute to a role - should we change it so that "all" in database includes replication connections? It certainly goe

Re: [HACKERS] replication and pg_hba.conf

2011-01-16 Thread Josh Berkus
> In 9.0, we specifically require using "replication" as database name > to start a replication session. In 9.1 we will have the REPLICATION > attribute to a role - should we change it so that "all" in database > includes replication connections? It certainly goes in the "principle > of least surp

Re: [HACKERS] replication and pg_hba.conf

2011-01-16 Thread Tom Lane
Magnus Hagander writes: > In 9.0, we specifically require using "replication" as database name > to start a replication session. In 9.1 we will have the REPLICATION > attribute to a role - should we change it so that "all" in database > includes replication connections? It certainly goes in the "p

[HACKERS] replication and pg_hba.conf

2011-01-16 Thread Magnus Hagander
In 9.0, we specifically require using "replication" as database name to start a replication session. In 9.1 we will have the REPLICATION attribute to a role - should we change it so that "all" in database includes replication connections? It certainly goes in the "principle of least surprise" path.