On Thu, 2007-06-21 at 11:17 +0000, Katsuhiko Okano wrote: > Description: PITR does not work in the case of recovery_target_xid = > 'SELECT_only_transaction_ID' > Details:
If a transaction is purely read only then there is no COMMIT or ABORT message written to the transaction log. As a result there is no way to know at what point that transaction occurred, nor any way to use the recovery_target_xid on those kinds of transactions. This is not a bug in PITR, it is a specific optimisation of WAL to improve the throughput of read-only queries. I'll add this to the docs in my next round of docs changes. How did you come to choose an xid of this nature? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
