Re: dump/restore problem

I've set the encoding to LATIN2 and everything worked fine... no encoding
errors and no memory allocation failures...

The tables where the memory failures occured are:

CREATE TABLE press_releases (
id serial NOT NULL,
title character varying(255) NOT NULL,
body text NOT NULL,
tdate date DEFAULT ('NOW'::text)::date NOT NULL
);

CREATE TABLE symbols (
id serial NOT NULL,
name character varying(255) NOT NULL,
description text NOT NULL
);

I was previously trying with encoding set to SQL_ASCII, because that was
the encoding of the database from which the data was taken from and where
everything was working fine with php, but I was having troubles with java
displaying the characters wrong... now I'm trying to see if with the data
converted to unicode works.

Thanks.

On Wed, 14 Jan 2004, Tom Lane wrote:

> Andrei Ivanov <andrei(dot)ivanov(at)ines(dot)ro> writes:
> > You will find more info attached.
>
> I could not reproduce the "out of memory" failure using this information
> (I got "invalid byte sequence" instead, on both of those COPY commands).
> What exactly is the declaration of the tables being copied into?
>
> > What about the invalid UNICODE data ? How can I fix it ?
>
> It looks like your data is in a single-byte encoding, perhaps latin1 or
> one of its siblings. To convert to unicode you will first have to
> identify just what encoding you're really using. Then put a "set
> client_encoding = whatever;" command at the top of the dump script (or
> set it in postgresql.conf, if that seems easier) and you should be able
> to import.
>
> regards, tom lane
>