Peter Landis <[EMAIL PROTECTED]> writes:
> but when restoring the database on the new server
> using the following command
> cat dbname.pgdump | psql dbname
> It generates the some of the tables and then somewhere
> in the middle of the process of restoreing the db I
> get the following error message:
> \? -- help
> \a -- toggle field-alignment (currently on)
> \C [<captn>] -- set html3 caption (currently '')
> Broken pipe
Hard to say much with so little information. Does anything show up
in the postmaster log? (If you're not running the postmaster with
stdout/stderr directed to a log file, you probably should be. And
don't forget NOT to use -S.)
My best guess based on just this is that psql or the backend is getting
confused about where the end of the COPY data is for one of the tables.
I think one way that could happen is if you have character set
differences --- eg, one installation compiled with MULTIBYTE and the
other not, or different LOCALE settings. Nothing else comes to mind
offhand. If that's not the answer, I'd suggest trying to narrow down
where in the dump file it's failing.
regards, tom lane
