| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | PITR: enhance getRecordTimestamp() |
| Date: | 2021-06-30 09:59:02 |
| Message-ID: | CANbhV-F+8=Y=cfurfD2hjoWVUvTk-Ot9BJdw2Myc=st3TsZy9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
For PITR, getRecordTimestamp() did not include all record types that
contain times.
Add handling for checkpoints, end of recovery and prepared xact record types.
Based on earlier discussions with community members.
Also, allow the option of recovery_target_use_origin_time = off (default) | on.
This allows PITR to consider whether it should use the local server
time of changes, or whether it should use the origin time on each
node. This is useful in multi-node data recovery.
This is part of a series of enhancements to PITR, in no specific order.
Passes make check and recovery testing; includes docs.
--
Simon Riggs http://www.EnterpriseDB.com/
| Attachment | Content-Type | Size |
|---|---|---|
| pitr_enhance_getRecordTimestamp.v1.patch | application/octet-stream | 6.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-06-30 11:05:06 | Re: Skipping logical replication transactions on subscriber side |
| Previous Message | Fabien COELHO | 2021-06-30 09:55:38 | Re: pgbench logging broken by time logic changes |