简体繁体 English

从存档的Wal日志中恢复Postgres流复制从设备

[英]Recover Postgres Streaming Replication Slave from Archived Wal Logs

原文 2018-02-20 06:07:31 5 1 postgresql

I have set up a Postgres Hot Standby server by Streaming Replication. 我已经通过流复制设置了Postgres Hot Standby服务器。 But My Standby server is asking for an old wal archive log which is currently not in Master's pg_xlog directory. 但是我的备用服务器要求一个旧的wal存档日志，该日志当前不在Master的pg_xlog目录中。 But the file exists in the wal archive backup directory. 但是该文件存在于wal归档备份目录中。

How can I configure Standby to read this file from backup directory? 如何配置备用数据库以从备份目录读取此文件？ Or any way to manually copy this file to Standby Server ? 或以任何方式手动将此文件复制到备用服务器？

Any help will be appreciated. 任何帮助将不胜感激。

1 个解决方案

You would have to add a restore_command to recovery.conf that can restore files from the WAL archive. 你将不得不增加一个restore_command到recovery.conf可以从WAL归档恢复文件。

Then restart the standby, and it should be able to recover. 然后重新启动备用数据库，它应该能够恢复。

When the standby cannot get the required WAL via streaming replication, it tries restore_command . 当备用服务器无法通过流复制获得所需的WAL时，它将尝试restore_command 。 When that fails, it tries streaming replication again, and so on in an endless loop. 如果失败，它将再次尝试流式复制，以此类推。

postgres 流复制 - 仅从属索引 - postgres streaming replication - slave only index

使用WAL的主从复制：Postgres uuid_generate_v4（）生成主键 - Master Slave replication using WAL: Postgres uuid_generate_v4() to generate primary key

定期删除 postgres 12 中存档的 Wal 文件 - Periodically deletion of archived Wal files in postgres 12

从生产到自定义从服务器的Postgres 9.6复制 - Postgres 9.6 replication from production to custom slave

Postgres 流式复制错误：请求的 WAL 段已被删除 - Postgres Streaming Replication Error: requested WAL segment has already been removed

如何恢复当前正在写入 master 且尚未归档的 wal 文件？ - How to recover the current wal file that was being written in master and not yet archived?

由于wal错误导致Postgres复制无法启动 - Postgres replication not starting due to wal error

Postgres中的流复制解决方案 - Streaming replication solution in Postgres

Postgres 流和逻辑复制 - Postgres Streaming and Logical Replication

流式复制因“WAL 段已被移动”而失败 - Streaming replication is failing with “WAL segment has already been moved”

暂无

暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 postgres 流复制 - 仅从属索引 - postgres streaming replication - slave only index 使用WAL的主从复制：Postgres uuid_generate_v4（）生成主键 - Master Slave replication using WAL: Postgres uuid_generate_v4() to generate primary key 定期删除 postgres 12 中存档的 Wal 文件 - Periodically deletion of archived Wal files in postgres 12 从生产到自定义从服务器的Postgres 9.6复制 - Postgres 9.6 replication from production to custom slave Postgres 流式复制错误：请求的 WAL 段已被删除 - Postgres Streaming Replication Error: requested WAL segment has already been removed 如何恢复当前正在写入 master 且尚未归档的 wal 文件？ - How to recover the current wal file that was being written in master and not yet archived? 由于wal错误导致Postgres复制无法启动 - Postgres replication not starting due to wal error Postgres中的流复制解决方案 - Streaming replication solution in Postgres Postgres 流和逻辑复制 - Postgres Streaming and Logical Replication 流式复制因“WAL 段已被移动”而失败 - Streaming replication is failing with “WAL segment has already been moved”

相关标签

粤ICP备18138465号 © 2020-2024 STACKOOM.COM