| From: | "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
| Cc: | "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com>, PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Recovery.conf and PITR |
| Date: | 2013-08-09 12:17:09 |
| Message-ID: | A71D4623-B71B-48FE-A6EF-D1E2B57C7AD0@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
On 9 Aug 2013, at 7:09 PM, Luca Ferrari wrote:
> 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?
Hi,
Is there a way to query the master (it is up and running) about the actual commit sequence by transaction IDs?
regards
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ascot.moss@gmail.com | 2013-08-09 13:07:59 | Recovery.conf and PITR by recovery_target_time |
| Previous Message | Ian Lawrence Barwick | 2013-08-09 12:12:49 | Re: archive folder housekeeping |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ascot.moss@gmail.com | 2013-08-09 13:07:59 | Recovery.conf and PITR by recovery_target_time |
| Previous Message | Ian Lawrence Barwick | 2013-08-09 12:12:49 | Re: archive folder housekeeping |