Simon Riggs wrote:
So we might have a pg_hba.conf that looks like this
TYPE DATABASEUSER CIDR-ADDRESS METHOD
host replication foo 192.168.0.5 md5
host replication foo 192.168.0.5 md5
Which looks pretty strange.
I think we should change that, though if not we
On Wed, Mar 24, 2010 at 8:22 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
but I don't see any mention of that in the docs. How about:
*** client-auth.sgml 24 Mar 2010 09:44:06 +0200 1.134
--- client-auth.sgml 24 Mar 2010 13:21:16 +0200
***
***
On Wed, 2010-03-24 at 20:30 +0900, Fujii Masao wrote:
On Wed, Mar 24, 2010 at 8:22 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
but I don't see any mention of that in the docs. How about:
+1
Yes, plus a mention in the rep docs.
That probably tips the balance towards
On Wed, Mar 24, 2010 at 8:52 PM, Simon Riggs si...@2ndquadrant.com wrote:
What's the word on when you guys will be finished with the open items
list for SR?
Sorry, I'm not sure when.
Now, I'm trying to address the open item Walreceiver is not
interruptible on win32.
It might take time to
On 24/03/2010 6:29 PM, Simon Riggs wrote:
So we are allowing a database to be called REPLICATION? Surely there
are some significant problems in that case. How will access control to
that database work in the pg_hba.conf?
Surely it should be consistent with template0 and postgres:
template1=#
