On 15 June 2017 at 23:12, Maeldron T. wrote:
> I could send an explicit command for each session to make it read-only
> I could use a read-only role (let’s ignore now I don’t use rules)
You can also set the GUC default_transaction_read_only = on.
But apps can easily clobber
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