| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tiemen Ruiten <t(dot)ruiten(at)tech-lab(dot)io> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: checkpoints taking much longer than expected |
| Date: | 2019-06-16 00:35:52 |
| Message-ID: | CAH2-Wz=dxjqDOKGenxbNj9U0gDd_skRat1pSV+XLfzb2PYc22A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jun 15, 2019 at 1:50 AM Tiemen Ruiten <t(dot)ruiten(at)tech-lab(dot)io> wrote:
> During normal operation I don't mind that it takes a long time, but when performing maintenance I want to be able to gracefully bring down the master without long delays to promote one of the standby's.
Maybe an "immediate" mode shutdown is appropriate, then. That will
mean that the primary will need to go through crash recovery if and
when you bring it back up, though.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Loftis | 2019-06-16 14:22:55 | Re: checkpoints taking much longer than expected |
| Previous Message | Noah Misch | 2019-06-15 18:37:59 | Re: pg_upgrade can result in early wraparound on databases with high transaction load |