PostgreSQL PITR 无法正常工作
PostgreSQL PITR not working properly
我正在尝试将 PostgreSQL 数据库恢复到某个时间点。
当我在 recovery.conf
中仅使用 restore_command
时,它工作正常。
restore_command = 'cp /var/lib/pgsql/pg_log_archive/%f %p'
当我使用 recovery_target_time parameter
时,它没有恢复到目标时间。
restore_command = 'cp /var/lib/pgsql/pg_log_archive/%f %p'
recovery_target_time='2018-06-05 06:43:00.0'
日志文件内容如下:
2018-06-05 07:31:39.166 UTC [22512] LOG: database system was interrupted; last known up at 2018-06-05 06:35:52 UTC
2018-06-05 07:31:39.664 UTC [22512] LOG: starting point-in-time recovery to 2018-06-05 06:43:00+00
2018-06-05 07:31:39.671 UTC [22512] LOG: restored log file "00000005.history" from archive
2018-06-05 07:31:39.769 UTC [22512] LOG: restored log file "00000005000000020000008F" from archive
2018-06-05 07:31:39.816 UTC [22512] LOG: redo starts at 2/8F000028
2018-06-05 07:31:39.817 UTC [22512] LOG: consistent recovery state reached at 2/8F000130
2018-06-05 07:31:39.818 UTC [22510] LOG: database system is ready to accept read only connections
2018-06-05 07:31:39.912 UTC [22512] LOG: restored log file "000000050000000200000090" from archive
2018-06-05 07:31:39.996 UTC [22512] LOG: recovery stopping before abort of transaction 9525, time 2018-06-05 06:45:02.088502+00
2018-06-05 07:31:39.996 UTC [22512] LOG: recovery has paused
我正在尝试将数据库实例恢复到 06:43:00。为什么恢复到 06:45:02?
编辑
在第一个场景中 recovery.conf 转换为 recovery.done 但在第二个场景中没有发生
这可能是什么原因?
您忘记设置了
recovery_target_action = 'promote'
时间点恢复后,recovery_target_action
确定 PostgreSQL 将如何进行。
默认值为pause
,这意味着 PostgreSQL 什么都不做,等待您告诉它如何继续。
要完成恢复,请连接到数据库并运行
SELECT pg_wal_replay_resume();
似乎在 06:43:00 和 06:45:02 之间没有数据库 activity 记录。观察日志显示 recovery stopping <strong>before</strong> abort of transaction 9525
.
我正在尝试将 PostgreSQL 数据库恢复到某个时间点。
当我在 recovery.conf
中仅使用 restore_command
时,它工作正常。
restore_command = 'cp /var/lib/pgsql/pg_log_archive/%f %p'
当我使用 recovery_target_time parameter
时,它没有恢复到目标时间。
restore_command = 'cp /var/lib/pgsql/pg_log_archive/%f %p'
recovery_target_time='2018-06-05 06:43:00.0'
日志文件内容如下:
2018-06-05 07:31:39.166 UTC [22512] LOG: database system was interrupted; last known up at 2018-06-05 06:35:52 UTC
2018-06-05 07:31:39.664 UTC [22512] LOG: starting point-in-time recovery to 2018-06-05 06:43:00+00
2018-06-05 07:31:39.671 UTC [22512] LOG: restored log file "00000005.history" from archive
2018-06-05 07:31:39.769 UTC [22512] LOG: restored log file "00000005000000020000008F" from archive
2018-06-05 07:31:39.816 UTC [22512] LOG: redo starts at 2/8F000028
2018-06-05 07:31:39.817 UTC [22512] LOG: consistent recovery state reached at 2/8F000130
2018-06-05 07:31:39.818 UTC [22510] LOG: database system is ready to accept read only connections
2018-06-05 07:31:39.912 UTC [22512] LOG: restored log file "000000050000000200000090" from archive
2018-06-05 07:31:39.996 UTC [22512] LOG: recovery stopping before abort of transaction 9525, time 2018-06-05 06:45:02.088502+00
2018-06-05 07:31:39.996 UTC [22512] LOG: recovery has paused
我正在尝试将数据库实例恢复到 06:43:00。为什么恢复到 06:45:02?
编辑
在第一个场景中 recovery.conf 转换为 recovery.done 但在第二个场景中没有发生
这可能是什么原因?
您忘记设置了
recovery_target_action = 'promote'
时间点恢复后,recovery_target_action
确定 PostgreSQL 将如何进行。
默认值为pause
,这意味着 PostgreSQL 什么都不做,等待您告诉它如何继续。
要完成恢复,请连接到数据库并运行
SELECT pg_wal_replay_resume();
似乎在 06:43:00 和 06:45:02 之间没有数据库 activity 记录。观察日志显示 recovery stopping <strong>before</strong> abort of transaction 9525
.