recovery_starts_paused is useless as it is. It pauses the recovery right after the first WAL record, all right, but before we see a running-xacts record, we won't let any backends in. And if you can't connect, you can't unpause, so it's stuck forever. It should probably behave as "pause after reaching WAL record that allows backends to connect". -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
On Fri, 2009-10-16 at 01:43 +0300, Heikki Linnakangas wrote: > recovery_starts_paused is useless as it is. It pauses the recovery right > after the first WAL record, all right, but before we see a running-xacts > record, we won't let any backends in. And if you can't connect, you > can't unpause, so it's stuck forever. Hmmm, strange. That was an earlier bug; I thought I'd fixed that. > It should probably behave as "pause after reaching WAL record that > allows backends to connect". Agreed, thanks. -- Simon Riggs www.2ndQuadrant.com
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера