Hi!
Thanks all for your help.
Now I can dump data from old dababase, but new problem came when I restore the
data to postgresql 7.4.
Error went out during the COPY command, if I do it in such command lines:
1. pg_dump news -f pgsql-database-news.sql #in ol
Hmm, you do realise that 6.5 is *really* *really* old. Who knows how many
bugs there are. There have been *5* major releases since and many more minor
ones.
I remember back then, 6.5 had many quirks that required a vacuum to fix (or
couldn't be fixed at all). I remember when creating a temporary t
hi,
The disk just had problem, I used fsck to fix it, But the problem
of database is still there.
After I read the postgresql document and found this:
--
COPY stops operation at the first error. This should not lead to problems in the event
of a COPY FROM, but the target relation will, of
On Thursday 04 December 2003 14:55, 吴德文 wrote:
> Help!
>
> A few days ago, my php page began to complain this:
> --
> Warning: PostgresSQL query failed: pqReadData() -- backend closed the
> channel unexpectedly. This probably means the backend terminated abnormally
> before or while processing
I would say you're loosing your disk drive. Have you lately checked for
bad blocks?
Jan
吴德文 wrote:
> Help!
>
> A few days ago, my php page began to complain this:
> --
> Warning: PostgresSQL query failed: pqReadData() -- backend closed the
> channel unexpectedly. This probably means the
