From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Pause at end of recovery |
Date: | 2011-12-20 17:15:08 |
Message-ID: | CA+U5nM+2JtZKiLhRfDVQL9kT6E6XjYQxC0rSpqEG3u-37BRczw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 20, 2011 at 1:40 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> These days we have pause_at_recovery_target, which lets us pause when
> we reach a PITR target. Is there a particular reason we don't have a
> way to pause at end of recovery if we *didn't* specify a target -
> meaning we let it run until the end of the archived log? While it's
> too late to change the target, I can see a lot of usescases where you
> don't want it to be possible to make changes to the database again
> until it has been properly verified - and keeping it up in readonly
> mode in that case can be quite useful...
Useful for what purpose? It' s possible to deny access in other ways already.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-12-20 17:32:13 | Re: Page Checksums |
Previous Message | Christopher Browne | 2011-12-20 17:12:56 | Re: Page Checksums |