pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Darley <pdarley@kinesis-cem.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pgsql-Admin <pgsql-admin@postgresql.org>
Subject: Re: Can't dump and restore
Date: Tue, 1 Nov 2005 13:40:06 -0800
Message-ID: <PDEOIIFFBIAABMGNJAGPMEFADPAA.pdarley@kinesis-cem.com> (raw)
In-Reply-To: <28279.1130880093@sss.pgh.pa.us>

Tom,
	As far as I can tell the source and destination dbs are SQL_ASCII, but I
have to admit I'm not sure how to find out.  When I dump just the schema for
the cluster, I get the following create database statements in the dump:

CREATE DATABASE neo WITH TEMPLATE = template0 OWNER = postgres ENCODING =
'SQL_ASCII';

	So it looks to me like it's using 'SQL_ASCII'.

	The dump I got from 7.? when I upgraded restored into 8.1 just fine.  This
is a dump from the 8.1.  I've done some tests this morning where I just dump
a table, create a temp database and try to restore the table into it.  I've
tried creating the db with different encodings and tried changing the line
"SET client_encoding = 'SQL_ASCII';" in the dump to "SET client_encoding =
'UNICODE';", and they have the same results.

	So, long and short, I think that everything should be SQL_ASCII, but even
when it is, I get the error.

Thanks,
Peter Darley

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, November 01, 2005 1:22 PM
To: Peter Darley
Cc: Pgsql-Admin
Subject: Re: [ADMIN] Can't dump and restore


"Peter Darley" <pdarley@kinesis-cem.com> writes:
> 	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.

Er, what is the encoding of the source database, exactly?  Is it the
same as the encoding of the destination database?

SQL_ASCII disables all encoding checks, so it's entirely plausible that
you would have byte sequences that are not legal Unicode in a SQL_ASCII
database.  If so, there's not much to do except manually clean up the
bogus data.

Also, if you're trying to restore into PG 8.1 from an older version,
we've fixed some mistakes in the Unicode encoding checker, so there
actually are differences in what the code will accept :-(

			regards, tom lane




view thread (5+ messages)  latest in thread

Message-ID: <PDEOIIFFBIAABMGNJAGPMEFADPAA.pdarley@kinesis-cem.com>
Permalink:  ../PDEOIIFFBIAABMGNJAGPMEFADPAA.pdarley@kinesis-cem.com/
Also on:    postgresql.org/message-id/PDEOIIFFBIAABMGNJAGPMEFADPAA.pdarley@kinesis-cem.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: pdarley@kinesis-cem.com, tgl@sss.pgh.pa.us
  Subject: Re: Can't dump and restore
  In-Reply-To: <PDEOIIFFBIAABMGNJAGPMEFADPAA.pdarley@kinesis-cem.com>
  References: <28279.1130880093@sss.pgh.pa.us> <PDEOIIFFBIAABMGNJAGPMEFADPAA.pdarley@kinesis-cem.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox