PostgreSQL - 如何恢复非常大的数据库

Lab*_*cle 8 postgresql dump restore pg-restore postgresql-9.1

当我尝试在我的devel数据库节点上恢复一个大型数据库(几乎是32Go自定义格式)时,我遇到了一个小问题(这个节点的RAM,CPU比我的生产服务器少).

我的数据库转储使用类似于以下的命令生成:

pg_dump -F custom -b myDB -Z 9 > /backup/myDB-`date +%y%m%d`.pg91
Run Code Online (Sandbox Code Playgroud)

当我恢复它时,我使用以下命令:

pg_restore -F custom -j 5 -d myDB /backup/myDB-20130331.pg91
Run Code Online (Sandbox Code Playgroud)

但是在这里,每次恢复命令失败时都会出现如下错误:

pg_restore: [archiver (db)] error returned by PQputCopyData: server closed the connection unexpectedly
This probably means the server terminated abnormally
    before or while processing the request.
pg_restore: [archiver] worker process failed: exit code 1
pg_restore: [archiver (db)] error returned by PQputCopyData: server closed the connection unexpectedly
This probably means the server terminated abnormally
    before or while processing the request.
pg_restore: [archiver (db)] error returned by PQputCopyData: server closed the connection unexpectedly
This probably means the server terminated abnormally
    before or while processing the request.
pg_restore: [archiver (db)] error returned by PQputCopyData: server closed the connection unexpectedly
This probably means the server terminated abnormally
    before or while processing the request.
Run Code Online (Sandbox Code Playgroud)

当我检查我的postgresql日志时,我可以读到这个:

   HINT:  In a moment you should be able to reconnect to the database and repeat your command.
   LOG:  all server processes terminated; reinitializing
   LOG:  database system was interrupted; last known up at 2013-04-02 11:41:48 UTC
   LOG:  database system was not properly shut down; automatic recovery in progress
   LOG:  redo starts at 86/26F302B0
   LOG:  unexpected pageaddr 85/E3F52000 in log file 134, segment 38, offset 16064512
   LOG:  redo done at 86/26F51FC0
   LOG:  last completed transaction was at log time 2013-04-02 11:50:47.663599+00
   LOG:  database system is ready to accept connections
   LOG:  autovacuum launcher started
Run Code Online (Sandbox Code Playgroud)

这很奇怪,我的postgresql服务器因为我的恢复而"重新启动".我尽量减少工作数量(-j 5选项),但仍然遇到同样的问题.但是,在具有更好规格的节点上,恢复此数据库没有问题.我不知道,但也许我的指标(其中一人是真正过大)的更新可能是一个线索来理解这个问题?

所以我有一些问题:是否有更好的方法来恢复真正庞大的数据库?我的pg_restore命令中是否遗漏了一些内容?可能是我的devel服务器的设置太低了?

任何线索将不胜感激.预先感谢.

环境:PostgreSQL 9.1(通过Debian软件包安装)

Lab*_*cle 11

对于这种大型工作,建议在恢复过程中禁用autovacuum(通过offpostgresql.conf中设置它).

它似乎终于适合我了.

  • 这对我有用 - 您能否提供有关为什么建议禁用“autovacuum”的来源(或更多信息),或者它具体做什么会导致数据库崩溃?谢谢! (3认同)