| From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, amul sul <sulamul(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [Patch] ALTER SYSTEM READ ONLY |
| Date: | 2020-06-18 15:08:38 |
| Message-ID: | 20200618170838.47524949@firost |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 18 Jun 2020 10:52:49 -0400
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
[...]
> But what you want is that if it does happen to go down for some reason before
> all the WAL is streamed, you can bring it back up and finish streaming the
> WAL without generating any new WAL.
Thanks to cascading replication, it could be very possible without this READ
ONLY mode, just in recovery mode, isn't it?
Regards,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-06-18 15:15:02 | Re: [patch] demote |
| Previous Message | Robert Haas | 2020-06-18 14:56:27 | Re: [Patch] ALTER SYSTEM READ ONLY |