Re: Recovery.conf and PITR
От | Luca Ferrari |
---|---|
Тема | Re: Recovery.conf and PITR |
Дата | |
Msg-id | CAKoxK+6jUd3Th5FG+Gm=_qB26XhODM8fHTR9wztCtf_LKJGKCQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Recovery.conf and PITR (wd <wd@wdicc.com>) |
Ответы |
Re: Recovery.conf and PITR
Recovery.conf and PITR by recovery_target_time |
Список | pgsql-general |
On Fri, Aug 9, 2013 at 12:40 PM, wd <wd@wdicc.com> wrote: > Try add these settings, > > pause_at_recovery_target=true Be warned that this would require a manual completion of the recovery and requires hot_standby that is not specified in the original post. > recovery_target_inclusive=false > Uhm...I guess the problem is not about the txid being included or not: the recovery target was 75634 and the transaction 75666 appeared, so the problem seems to be an out-of-order commit of the transactions. In such case making the inclusive false will not cause 75666 to appear if it has committed before the target xid, or am I wrong? Luca
В списке pgsql-general по дате отправления: