On Tue, Dec 20, 2011 at 1:40 PM, Magnus Hagander <mag...@hagander.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
