| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: dividing privileges for replication role. |
| Date: | 2013-01-21 01:57:35 |
| Message-ID: | 50FCA08F.8000801@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Katsumata-san,
> In this patch, I made below.
> a) adding new privileges for replication:"MASTER REPLICATION" and "CASCADE
> REPLICATION"
> "MASTER REPLICATION": Replication-connection to master server is only
> allowed
> "CASCADE REPLICATION": Replication-connection to cascade server is only
> allowed
> ("REPLICATION" already implemented means replication-connection to both
> servers is allowed)
This seems to me a case of making things more complicated for everyone
in order to satisfy a very narrow use-case. It certainly doesn't seem
to me to do anything about the "accidental cycle" issue. Am I missing
something?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2013-01-21 02:01:29 | Re: Making testing on Windows easier |
| Previous Message | Craig Ringer | 2013-01-21 01:13:03 | Re: WIP patch for hint bit i/o mitigation |