pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Scott Eade <seade@backstagetech.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Converting from LATIN1 to UNICODE encoding?
Date: Wed, 21 Sep 2005 10:40:32 -0400
Message-ID: <20050921144032.GD24138@surnet.cl> (raw)
In-Reply-To: <433116DF.7050108@backstagetech.com.au>
References: <433116DF.7050108@backstagetech.com.au>

On Wed, Sep 21, 2005 at 06:16:31PM +1000, Scott Eade wrote:
> I have a database that was created using the LATIN1 encoding.
> 
> Is it necessary for me to convert the database to some other encoding
> (e.g. UNICODE) before I can store non-LATIN1 characters or does
> PostgreSQL catch these and encode them somehow?
> 
> I have actually been attempting to convert a database by doing a pg_dump
> (from the LATIN1 database) followed by a pg_restore (to one created with
> the UNICODE encoding).  Seemed to work with a sparsely populated 8.0.3
> database, but I am running into all sorts of problems with 7.3.10 (e.g.
> corrupted database followed by corrupted pg_clog).

Hmm.  Do tell, what database did you use as template?  Was it correctly
frozen?  If not, has it suffered from Xid wraparound?

Try dumping the template database.  If it succeeds, then it's OK.  If it
complains in the same way, with a missing pg_clog file, there lies the
problem.

-- 
Alvaro Herrera                                http://www.planetpostgresql.org
"En las profundidades de nuestro inconsciente hay una obsesiva necesidad
de un universo lógico y coherente. Pero el universo real se halla siempre
un paso más allá de la lógica" (Irulan)



view thread (3+ messages)

Message-ID: <20050921144032.GD24138@surnet.cl>
Permalink:  ../20050921144032.GD24138@surnet.cl/
Also on:    postgresql.org/message-id/20050921144032.GD24138@surnet.cl

 · 

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: alvherre@alvh.no-ip.org, seade@backstagetech.com.au
  Subject: Re: Converting from LATIN1 to UNICODE encoding?
  In-Reply-To: <20050921144032.GD24138@surnet.cl>
  References: <433116DF.7050108@backstagetech.com.au> <20050921144032.GD24138@surnet.cl>

* 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