Skip site navigation (1) Skip section navigation (2)

BUG #3401: PITR does not work in the case of recovery_target_xid = 'SELECT_only_transaction_ID'

From: "Katsuhiko Okano" <okano(dot)katsuhiko(at)oss(dot)ntt(dot)co(dot)jp>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3401: PITR does not work in the case of recovery_target_xid = 'SELECT_only_transaction_ID'
Date: 2007-06-21 11:17:59
Message-ID: 200706211117.l5LBHxOv078390@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      3401
Logged by:          Katsuhiko Okano
Email address:      okano(dot)katsuhiko(at)oss(dot)ntt(dot)co(dot)jp
PostgreSQL version: Head(20070607)
Operating system:   Fedora Core release 5 (Bordeaux)
Description:        PITR does not work in the case of recovery_target_xid =
'SELECT_only_transaction_ID'
Details: 

Transaction ID is wasted even if it is a transaction containing only
SELECT.
Transaction ID can be specified when recovering using a PITR feature.
For example, in recovery.conf,
--------
recovery_target_xid = '1100842'
--------

A PITR feature does not work in the case which specified transaction ID in
recovery_target_xid
corresponding to the transaction which contains only SELECT
It expects to stop in foward of target ID or in backward of target ID.
However, it does not stop while recovery done.
Recovery is done to the last and it becomes the newest.(target ID is
disregarded)

This operation is unexpected.I think that it should describe on a document.

Responses

pgsql-bugs by date

Next:From: Andrew SullivanDate: 2007-06-21 15:05:25
Subject: Re: FW: BUG #3400: System Hang occur
Previous:From: hyukjooDate: 2007-06-21 09:01:03
Subject: FW: BUG #3400: System Hang occur

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group