| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Katsuhiko Okano" <okano(dot)katsuhiko(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #3401: PITR does not work in the case ofrecovery_target_xid = 'SELECT_only_transaction_ID' |
| Date: | 2007-06-22 07:38:39 |
| Message-ID: | 1182497919.9276.44.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Katsuhiko Okano | 2007-06-22 09:06:48 | Re: BUG #3401: PITR does not work in the case ofrecovery_target_xid = 'SELECT_only_transaction_ID' |
| Previous Message | Zdenek Kotala | 2007-06-22 07:27:07 | Re: BUG #3403: ver 8.2 can't add serial column to temp table,but 8.1 can |