From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Clayton Cottingham <drfrog(at)smartt(dot)com> |
Cc: | pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: [SQL] pg_dumpall + psql -e template1 |
Date: | 1999-09-24 22:42:09 |
Message-ID: | 7131.938212929@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Clayton Cottingham <drfrog(at)smartt(dot)com> writes:
> when i dump out all dbspg_dumpall>dbs.out and try to put into a new
> installation psql -e template1 <dbs.out it always fails when trying to
> copy the actual data
> usually producing errors that result in the \? listings and then a seq
> fault
There have been some reports that COPY in/out is not careful enough
about quoting control characters and so forth, so if you have text
fields containing control characters you might run into a problem
like the above.
As a quick workaround, try the pg_dump switch to dump data as INSERT
statements instead of with COPY. It'll be a lot slower to load :(
but if it avoids the problem then this is probably the correct
diagnosis.
If you can track down exactly what data is making COPY misbehave,
we'd have a better shot at fixing the bug.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | omid omoomi | 1999-09-25 04:04:24 | RE: [SQL] comparing 2 tables. . . |
Previous Message | Clayton Cottingham | 1999-09-24 21:47:14 | pg_dumpall + psql -e template1 |