| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | amul sul <sulamul(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [Patch] ALTER SYSTEM READ ONLY |
| Date: | 2020-06-18 14:54:22 |
| Message-ID: | CA+Tgmoa7bwWuUPHk3c2dzO+vMaM=CmciUo1OWaHSg49jG9-4pg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 18, 2020 at 7:19 AM amul sul <sulamul(at)gmail(dot)com> wrote:
> Let me explain the case, if we do skip the end-of-recovery checkpoint while
> starting the system in read-only mode and then later changing the state to
> read-write and do a few write operations and online checkpoints, that will be
> fine? I am yet to explore those things.
I think we'd want the FIRST write operation to be the end-of-recovery
checkpoint, before the system is fully read-write. And then after that
completes you could do other things.
It would be good if we can get an opinion from Andres about this,
since I think he has thought about this stuff quite a bit.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-06-18 14:56:27 | Re: [Patch] ALTER SYSTEM READ ONLY |
| Previous Message | Robert Haas | 2020-06-18 14:52:49 | Re: [Patch] ALTER SYSTEM READ ONLY |