| From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
|---|---|
| To: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Recovery.conf and PITR |
| Date: | 2013-08-09 11:09:40 |
| Message-ID: | CAKoxK+6jUd3Th5FG+Gm=_qB26XhODM8fHTR9wztCtf_LKJGKCQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
On Fri, Aug 9, 2013 at 12:40 PM, wd <wd(at)wdicc(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lawrence Barwick | 2013-08-09 12:12:49 | Re: archive folder housekeeping |
| Previous Message | Romain Billon-Grand | 2013-08-09 10:40:29 | Re: BUG #8335: trim() un-document behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lawrence Barwick | 2013-08-09 12:12:49 | Re: archive folder housekeeping |
| Previous Message | wd | 2013-08-09 10:40:04 | Re: Recovery.conf and PITR |