| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Add connection messages for streaming replication. |
| Date: | 2010-03-24 10:49:48 |
| Message-ID: | 3f0b79eb1003240349i7151da8bi7a8fba4a4708de3b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Mar 24, 2010 at 7:29 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> So we are allowing a database to be called "REPLICATION"?
Yes.
> Surely there
> are some significant problems in that case. How will access control to
> that database work in the pg_hba.conf?
We can do that by enclosing the database field of pg_hba.conf in double
quotes as follows.
TYPE DATABASE USER CIDR-ADDRESS METHOD
host "replication" foo 192.168.0.5 md5
In pg_hba.conf, double-quoted keyword like "all", "sameuser", "samerole"
or "replication" matches a database with that name.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-03-24 11:09:00 | Re: [COMMITTERS] pgsql: Add connection messages for streaming replication. |
| Previous Message | Simon Riggs | 2010-03-24 10:29:56 | Re: [COMMITTERS] pgsql: Add connection messages for streaming replication. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-03-24 11:09:00 | Re: [COMMITTERS] pgsql: Add connection messages for streaming replication. |
| Previous Message | Simon Riggs | 2010-03-24 10:29:56 | Re: [COMMITTERS] pgsql: Add connection messages for streaming replication. |