From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Checkpoints vs restartpoints |
Date: | 2015-06-09 23:20:19 |
Message-ID: | CAEepm=3DcBoVWxHieBiooixmgnz3cCgEnwSrmRH9hCTmw1hgpA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
Why do standby servers not simply treat every checkpoint as a
restartpoint? As I understand it, setting checkpoint_timeout and
checkpoint_segments higher on a standby server effectively instruct
standby servers to skip some checkpoints. Even with the same settings
on both servers, the server could still choose to skip a checkpoint
near the checkpoint_timeout limit due to the vagaries of time keeping
(though I suppose it's very unlikely). But what could the advantage
of skipping checkpoints be? Do people deliberately set hot standby
machines up like this to trade a longer crash recover time for lower
write IO?
I was wondering about this in the context of the recent multixact
work, since such configurations could leave you with different SLRU
files on disk which in some versions might change the behaviour in
interesting ways.
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2015-06-09 23:31:43 | Re: Draft release notes for 9.4.4 et al |
Previous Message | Bruce Momjian | 2015-06-09 22:35:08 | The purpose of the core team |