From postgreSQL mailing list it is stated that:
I'd only expect this if an old pg_dumpall was being used
It occurs, when dealing with a version so old that the behavior of COPY itself was different.
One possible workaround is to use the --inserts option of pg_dump. That will mean slower dump and restore, though.
refer here
.
Also worth referring here.