Can't dump and restore

From: "Peter Darley" <pdarley(at)kinesis-cem(dot)com>
To: "Pgsql-Admin" <pgsql-admin(at)postgresql(dot)org>
Subject: Can't dump and restore
Date: 2005-11-01 18:52:20
Message-ID: PDEOIIFFBIAABMGNJAGPIEEPDPAA.pdarley@kinesis-cem.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Folks,

I'm having some trouble restoring data that was dumped from my database.
When I dump out a table (pg_dump -d neo -t question > question.tbl) and try
to restore it (psql -d temp -f question.tbl) I get errors on certain rows:
"psql:question.tbl:15861: ERROR: invalid byte sequence for encoding
"UNICODE": 0xe96520". This happens when I use SQL_ASCII or UNICODE as the
encoding. I didn't try any other encodings.

When I do this with a table, it's missing the rows that throw the error.
When I do it with a full database dump, the tables that have rows that throw
the errors are empty (I assume it's just cancleing the transaction).

What is confounding me is that this is data that is currently in the
database, unless the dump is creating errors as it goes, which doesn't seem
likely. It is always the same rows as well. Why would it be rejecting data
that it obvously accepted once?

The computer is running FC4 64 SMP. The version() of PostgreSQL is: "Linux
version 2.6.13-1.1526_FC4smp (bhcompile(at)hs20-bc1-1(dot)build(dot)redhat(dot)com) (gcc
version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Wed Sep 28 19:28:24 EDT
2005"

Does anyone have any idea of what might be going on here? Is this likely
to be something that I can fix, or should I start taring up the directory
when I need to do backups?

Thanks,
Peter Darley

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Warren Little 2005-11-01 20:05:15
Previous Message Diego 2005-11-01 18:09:24 UNIQUE KEY with null value...