pg_restore 重复键和无效命令错误

Posted

技术标签:

【中文标题】pg_restore 重复键和无效命令错误【英文标题】:pg_restore duplicate key and invalid command errors 【发布时间】:2016-06-22 11:14:10 【问题描述】:

Postgres 版本:

PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3), 64-bit

我们使用 vm 转换器将我们的系统从一台服务器转移到另一台服务器(使用更好的 cpu 和内存),当我尝试备份数据库时出现错误:

pg_dump: reading schemas 
pg_dump: reading user-defined tables 
pg_dump: reading extensions 
pg_dump: reading user-defined functions 
pg_dump: reading user-defined types 
pg_dump: reading procedural languages 
pg_dump: reading user-defined aggregate functions 
pg_dump: reading user-defined operators 
pg_dump: reading user-defined operator classes 
pg_dump: reading user-defined operator families 
pg_dump: reading user-defined text search parsers 
pg_dump: reading user-defined text search templates 
pg_dump: reading user-defined text search dictionaries 
pg_dump: reading user-defined text search configurations 
pg_dump: reading user-defined foreign-data wrappers 
pg_dump: reading user-defined foreign servers 
pg_dump: reading default privileges 
pg_dump: reading user-defined collations 
pg_dump: reading user-defined conversions 
pg_dump: reading type casts 
pg_dump: reading table inheritance information 
pg_dump: reading rewrite rules 
pg_dump: finding extension members 
pg_dump: finding inheritance relationships 
pg_dump: reading column info for interesting tables 
pg_dump: finding the columns and types of table "account_account" 
pg_dump: [archiver (db)] query failed: ERROR:  missing chunk number 0 for toast value 3297740 in pg_toast_2619 
pg_dump: [archiver (db)] query was: SELECT a.attnum, a.attname, a.atttypmod, a.attstattarget, a.attstorage, t.typstorage, a.attnotnull, a.atthasdef, a.attisdropped, a.attlen, a.attalign, a.attislocal, pg_catalog.format_type(t.oid,a.atttypmod) AS atttypname, array_to_string(a.attoptions, ', ') AS attoptions, CASE WHEN a.attcollation <> t.typcollation THEN a.attcollation ELSE 0 END AS attcollation, pg_catalog.array_to_string(ARRAY(SELECT pg_catalog.quote_ident(option_name) || ' ' || pg_catalog.quote_literal(option_value) FROM pg_catalog.pg_options_to_table(attfdwoptions) ORDER BY option_name), E', 
    ') AS attfdwoptions FROM pg_catalog.pg_attribute a LEFT JOIN pg_catalog.pg_type t ON a.atttypid = t.oid WHERE a.attrelid = '274619'::pg_catalog.oid AND a.attnum > 0::pg_catalog.int2 ORDER BY a.attrelid, a.attnum

我使用reindexdb 解决了它,在我尝试pg_dump -U postgres my_db &gt; /home/mydb.backup 之后它成功了。然后我尝试恢复数据库以确保备份有效

psql -U postgres new_db < /home/mydb.backup

并且有一个错误:

ERROR : extra data after last expected column 
Context: COPY tbl1, line1: "1 2013-12-02 2013-12-02  9387.74  9775.46211485490864940000"   6180.9500000000   80262 ...." 
ERROR : column "id" of relation "tbl1" does not exists 
invalid command \N 
invalid command \N 
invalid command \N 
..... 
invalid command \N 
invalid command \. 
ERROR:  syntax error at or near "87685" 
LINE 1: 87685 SO87690 1 170468 2015-05-30 2015 05 30 
        ^ 
invalid command \. 

ERROR:  duplicate key value violates unique constraint "ir_act_client_pkey" 
DETAIL:  Key (id)=(103) already exists. 
CONTEXT:  COPY ir_act_client, line 21: "" 
ERROR:  duplicate key value violates unique constraint "ir_act_report_xml_pkey" 
DETAIL:  Key (id)=(733) already exists. 
CONTEXT:  COPY ir_act_report_xml, line 59: "" 
ERROR:  duplicate key value violates unique constraint "ir_act_server_pkey" 
DETAIL:  Key (id)=(703) already exists. 
CONTEXT:  COPY ir_act_server, line 6: "" 
ERROR:  duplicate key value violates unique constraint "ir_act_window_pkey" 
DETAIL:  Key (id)=(1) already exists. 
CONTEXT:  COPY ir_act_window, line 235: "334    Last Product Inventories        ir.actions.act_window   \N      1       2013-07-03 10:39:48.399509  2013-12-16 16:38:..." 
ERROR:  duplicate key value violates unique constraint "ir_act_window_group_rel_act_id_gid_key" 
DETAIL:  Key (act_id, gid)=(76, 1) already exists. 
CONTEXT:  COPY ir_act_window_group_rel, line 14: "" 
ERROR:  duplicate key value violates unique constraint "ir_act_window_view_pkey" 
DETAIL:  Key (id)=(100) already exists. 
CONTEXT:  COPY ir_act_window_view, line 88: ""

如何解决?

【问题讨论】:

请尝试使用 pg_dump -Fc 进行转储,看看会得到什么 @e4c5 感谢您的建议,由于数据库已加载,我现在无法备份,今晚我会尝试。 我尝试使用 -Fc 并且文件在备份 12GB 之后,数据库是 20GB,没有 -Fc 的旧文件是 30GB,现在当我尝试恢复这个 12GB 文件时出现错误ERROR: syntax error AT OR near "PGDMP" LINE 1: PGDMPREVOKE ALL ON SCHEMA public FROM postgres; ^ GRANT GRANT GRANT ERROR: syntax error AT OR near "" LINE 1: "position" INTEGER, ^ ERROR: syntax error AT OR near "" LINE 1: LANGUAGE c STRICT pg_dump 的输出是通过 pg_restore 而不是 psql 来恢复的 @e4c5 我尝试pg_restore -C -d postgres --disable-triggers /.../../... 并得到一些错误pastebin.com/r2TwSAPb 但现在恢复仍在继续 【参考方案1】:

当您导出数据时,使用带有 -Fc 选项的 pg_dump。

输出适合输入到 pg_restore 的自定义格式存档。 与目录输出格式一起,这是最灵活的 输出格式,因为它允许手动选择和重新排序 恢复期间的归档项目。这种格式也被压缩 默认。

紧凑的格式使服务器之间的传输更容易,并且根据您的 IO 负载,转储和恢复也可能更快。

如果您打算将数据导入到已经包含一些表的数据库中,那么复杂性是不可避免的。您可以通过使用 --clean 选项进行转储来克服这种情况。

【讨论】:

【参考方案2】:

以下命令帮助我摆脱了这些错误:

pg_dump:运行

pg_dump -O -d 数据库名 > 文件名.sql

使用 -O 选项(以消除与所有者相关的错误。)

pg_restore:

确保在运行数据库恢复命令之前,数据库中不存在任何表。 (否则这会导致一些错误,包括违反关键约束等)RUN

psql -1 数据库名

使用 -1 选项确保数据库已完全导入或根本不导入。 执行也会在第一个错误处停止,从而更容易一次解决一个错误。

【讨论】:

以上是关于pg_restore 重复键和无效命令错误的主要内容,如果未能解决你的问题,请参考以下文章

PgSql备份pg_dump与还原手记pg_restore

pg_restore错误:pg_restore:文件头中的[archiver]不支持的版本(1.13)

如何在 Windows 命令行上使用 pg_restore?

获取无效 POST、PATCH 的 CORS 错误 - REST 端点

Postgres.app:pg_restore 挂起

Django Rest Framework 中的 JWT 身份验证错误“无效签名”