| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Maeldron T(dot)" <maeldron(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical replication read-only slave |
| Date: | 2017-06-15 15:25:59 |
| Message-ID: | 5f7dbc85-a798-7ce7-5ce3-7d8a1913cd86@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/15/17 11:12, Maeldron T. wrote:
> However, it provides me a safety net that I could not execute writes on
> the slave by accident. Not only I couldn’t do it, I would also receive a
> notification from the software about the attempt as it would throw an
> exception.
>
> Let’s say I would switch to logical replication of all tables
> Safety net is gone
You can change the permissions on your slave so that you cannot write to
the tables.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-06-15 15:40:50 | Re: Making server name part of the startup message |
| Previous Message | Maeldron T. | 2017-06-15 15:12:00 | logical replication read-only slave |