我遵循了所有这些例子，它们都失败了，出现了我们正在谈论的错误:

在Postgres中将一个表从一个数据库复制到另一个数据库

有效的是使用-C的语法，请看这里:

pg_dump -C -t tableName "postgres://$User:$Password@$Host:$Port/$DBName" | psql "postgres://$User:$Password@$Host:$Port/$DBName"

此外，如果两者之间有不同的模式，我发现改变一个dB的模式以匹配其他的表副本是必要的，例如:

DROP SCHEMA public;
ALTER SCHEMA originalDBSchema RENAME TO public;

In my recent experience, it's possible to get this error when the real problem has nothing to do with escape characters or newlines. In my case, I had created a dump from database A with pg_dump -a -t table_name > dump.sql and was trying to restore it to database B with psql < dump.sql (after updating the proper env vars, of course) What I finally figured out was that the dump, though it was data-only (the -a option, so that the table structure isn't explicitly part of the dump), was schema-specific. That meant that without manually modifying the dump, I couldn't use a dump generated from schema1.table_name to populate schema2.table_name. Manually modifying the dump was easy, the schema is specified in the first 15 lines or so.

Adding my resolution, incase it helps anyone. I installed postgis but the error wasn't resolved. The --inserts option was not feasible as I had to copy a big schema having tables with thousands of rows. For the same database I didn't see this issue when pg_dump and psql (restore) were run on mac. But the issue came when pg_dump was run on linux machine, the dump file copied to mac and tried for restore. So I opened the dump file in VSCode. It detected unusual line terminators and gave option to remove them. After doing that the dump file restore ran without the invalid command \N errors.

Postgres使用\N作为NULL值的替代符号。但是所有psql命令都以反斜杠\符号开始。当复制语句失败，但转储的加载仍在继续时，您可以获得这些消息。这条消息是假警报。如果希望看到COPY语句失败的真正原因，则必须搜索此错误之前的所有行。

可以切换psql到“第一个错误停止”模式，并找到错误:

psql -v ON_ERROR_STOP=1

大多数时候，解决方案是安装postgres-contrib包。

可以使用INSERTS语句和——INSERTS参数生成转储。