pg_restore 重复键和无效命令错误
pg_restore duplicate key and invalid command errors
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 > /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 选项。
Output a custom-format archive suitable for input into pg_restore.
Together with the directory output format, this is the most flexible
output format in that it allows manual selection and reordering of
archived items during restore. This format is also compressed by
default.
紧凑的格式使得在服务器之间传输更容易，并且根据您的 IO 负载甚至可能更快地转储和恢复。
如果您打算将数据导入到已经包含一些表的数据库中，那么复杂性是不可避免的。您可以通过使用 --clean 选项进行转储来克服这种情况。
以下命令帮助我摆脱了这些错误：
pg_dump:
运行
pg_dump -O -d database_name > file_name.sql
- 使用 -O 选项（以消除与所有者相关的错误。）
pg_restore:
- 确保在运行数据库恢复命令之前，数据库中不存在任何表。 （否则会导致一些错误，包括违反关键约束等）
运行
psql -1 database_name < file_name.sql
- 使用 -1 选项确保数据库已完全导入或根本没有导入。
- 执行也会在第一个错误处停止，这样更容易一次解决一个错误。
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 > /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 选项。
Output a custom-format archive suitable for input into pg_restore. Together with the directory output format, this is the most flexible output format in that it allows manual selection and reordering of archived items during restore. This format is also compressed by default.
紧凑的格式使得在服务器之间传输更容易，并且根据您的 IO 负载甚至可能更快地转储和恢复。
如果您打算将数据导入到已经包含一些表的数据库中，那么复杂性是不可避免的。您可以通过使用 --clean 选项进行转储来克服这种情况。
以下命令帮助我摆脱了这些错误：
pg_dump:
运行
pg_dump -O -d database_name > file_name.sql
- 使用 -O 选项（以消除与所有者相关的错误。）
pg_restore:
- 确保在运行数据库恢复命令之前，数据库中不存在任何表。 （否则会导致一些错误，包括违反关键约束等）
运行
psql -1 database_name < file_name.sql
- 使用 -1 选项确保数据库已完全导入或根本没有导入。
- 执行也会在第一个错误处停止，这样更容易一次解决一个错误。