| From: | Debraj Manna <subharaj(dot)manna(at)gmail(dot)com> |
|---|---|
| To: | Robert Zenz <robert(dot)zenz(at)sibvisions(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Stopping writes in master |
| Date: | 2018-06-14 11:23:37 |
| Message-ID: | CAF6DVKOxxOJgG36zKjqwCd8oNOLAqmpOxCFCMWs6Bs7owBVd8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Yes I want to switch the database to read-only mode. The existing
connections should also be not able to write.
On Thu 14 Jun, 2018, 4:37 PM Robert Zenz, <robert(dot)zenz(at)sibvisions(dot)com>
wrote:
> Can existing connections be dropped or do they need to stay established?
> Also,
> are you trying to switch the database to a read-only mode for backup
> purposes or
> something different?
>
>
> On 14.06.2018 12:46, Debraj Manna wrote:
> > Hi
> >
> > In a 3 node cluster with 1 master and 2 slaves with postgres 10.4 is
> there
> > any configuration setting that will stop all writes to the master from
> the
> > client. But the clients can read data from master and other slaves ?
> >
> > Thanks,
> >
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wei Shan | 2018-06-14 12:04:53 | Re: BTree index support prefix compression |
| Previous Message | Robert Zenz | 2018-06-14 11:06:41 | Re: Stopping writes in master |