Hi -

In previous versions of postgres (8.1, 8.0), we had problems loading
some data from dumps that were used the copy command rather than the
insert command. If I remember correctly, these problems were caused by
weird characters in some of the data values. As a result, we tend to use
the -d option with pg_dump. At this point our databases are taking too
long to reload using inserts. I did some testing and haven't run into
the problems with the copy commands but don't want to find out that I
was wrong when I'm trying to restore from a failure.

Were there changes made some time before 8.2.4 that made loading pg_dump
with copy as safe as with insert commands? Have other people had
problems restoring databases from pg_dump without the -d option?

Mija


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Mija Lee <mija@scharp.org> writes:
> In previous versions of postgres (8.1, 8.0), we had problems loading
> some data from dumps that were used the copy command rather than the
> insert command. If I remember correctly, these problems were caused by
> weird characters in some of the data values. As a result, we tend to use
> the -d option with pg_dump.

As far as I can find from a quick look through the CVS logs, no
data-mangling bug in COPY has been reported or fixed since before 7.4
(at least in the mainline code --- CSV mode has had some teething pains,
but pg_dump has never used CSV mode). The last patch I can find that
addressed any such problem was here:
http://archives.postgresql.org/pgsql...0/msg00050.php

If you've had issues since then, you really should have filed bug
reports.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly