无法在 Postgresql-10.0 上恢复数据库备份
Unable to restore database backup on Postgresql-10.0
我在 Linux 机器 (RHEL 7.4) 上使用 postgresql-9.4（端口 5432）和 postgresql-10.0（端口 5433）。 Postgresql-9.4 是使用 yum 存储库安装的，Postgresql-10.0 是使用不同分区中的源安装的。
我已经使用 pg_dump 在 Postgresql-9.4 上备份了数据库 (dtbase.backup)，并尝试使用 pg_restore.[=11 在 Postgresql-10.0 上恢复它=]
执行此操作时，出现以下错误：
pg_restore: [archiver] unsupported version (1.13) in file header
我查看了不同的论坛，但无法找到解决方案。任何帮助将不胜感激。
您必须将 PostgreSQL v10 升级到 10.3 才能提交 b8a2908f0ac735da68d49be2bce2d523e363f67b:
Avoid using unsafe search_path settings during dump and restore.
Historically, pg_dump has "set search_path = foo, pg_catalog" when
dumping an object in schema "foo", and has also caused that setting
to be used while restoring the object. This is problematic because
functions and operators in schema "foo" could capture references meant
to refer to pg_catalog entries, both in the queries issued by pg_dump
and those issued during the subsequent restore run. That could
result in dump/restore misbehavior, or in privilege escalation if a
nefarious user installs trojan-horse functions or operators.
This patch changes pg_dump so that it does not change the search_path
dynamically. The emitted restore script sets the search_path to what
was used at dump time, and then leaves it alone thereafter. Created
objects are placed in the correct schema, regardless of the active
search_path, by dint of schema-qualifying their names in the CREATE
commands, as well as in subsequent ALTER and ALTER-like commands.
Since this change requires a change in the behavior of pg_restore
when processing an archive file made according to this new convention,
bump the archive file version number; old versions of pg_restore will
therefore refuse to process files made with new versions of pg_dump.
Security: CVE-2018-1058
您的 9.4 安装已经使用了 1.13 的存档格式，您的 v10 安装尚不支持。
此外，您应该始终使用pg_dump更高版本的PostgreSQL来升级数据库。
我在 Linux 机器 (RHEL 7.4) 上使用 postgresql-9.4（端口 5432）和 postgresql-10.0（端口 5433）。 Postgresql-9.4 是使用 yum 存储库安装的，Postgresql-10.0 是使用不同分区中的源安装的。
我已经使用 pg_dump 在 Postgresql-9.4 上备份了数据库 (dtbase.backup)，并尝试使用 pg_restore.[=11 在 Postgresql-10.0 上恢复它=]
执行此操作时，出现以下错误：
pg_restore: [archiver] unsupported version (1.13) in file header
我查看了不同的论坛，但无法找到解决方案。任何帮助将不胜感激。
您必须将 PostgreSQL v10 升级到 10.3 才能提交 b8a2908f0ac735da68d49be2bce2d523e363f67b:
Avoid using unsafe search_path settings during dump and restore.
Historically, pg_dump has "set search_path = foo, pg_catalog" when
dumping an object in schema "foo", and has also caused that setting
to be used while restoring the object. This is problematic because
functions and operators in schema "foo" could capture references meant
to refer to pg_catalog entries, both in the queries issued by pg_dump
and those issued during the subsequent restore run. That could
result in dump/restore misbehavior, or in privilege escalation if a
nefarious user installs trojan-horse functions or operators.
This patch changes pg_dump so that it does not change the search_path
dynamically. The emitted restore script sets the search_path to what
was used at dump time, and then leaves it alone thereafter. Created
objects are placed in the correct schema, regardless of the active
search_path, by dint of schema-qualifying their names in the CREATE
commands, as well as in subsequent ALTER and ALTER-like commands.
Since this change requires a change in the behavior of pg_restore
when processing an archive file made according to this new convention,
bump the archive file version number; old versions of pg_restore will
therefore refuse to process files made with new versions of pg_dump.
Security: CVE-2018-1058
您的 9.4 安装已经使用了 1.13 的存档格式，您的 v10 安装尚不支持。
此外，您应该始终使用pg_dump更高版本的PostgreSQL来升级数据库。