From: | Andrei Ivanov <andrei(dot)ivanov(at)ines(dot)ro> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: dump/restore problem |
Date: | 2004-01-14 08:02:31 |
Message-ID: | Pine.LNX.4.58L0.0401140947160.2355@webdev.ines.ro |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
You will find more info attached.
What about the invalid UNICODE data ? How can I fix it ? In the attachment
there is the line that gives the error...
Thanks.
On Tue, 13 Jan 2004, Tom Lane wrote:
> Andrei Ivanov <andrei(dot)ivanov(at)ines(dot)ro> writes:
> > I have a dump created with pg_dump ver 7.4.1 from a postgres 7.4 database,
> > with encoding SQL_ASCII.
> > I'm trying to import this dump in a 7.4.1 postgres database with encoding
> > UNICODE, but I'm getting some errors:
>
> > psql:dump.sql:1277: ERROR: invalid memory alloc request size
> > 1073741824
> > psql:dump.sql:3490: ERROR: invalid byte sequence for encoding
> > "UNICODE": 0xce20
>
> The "invalid byte sequence" problem occurs because you are trying to
> load data that isn't valid UNICODE. You need to fix the data.
>
> I'm more interested in the "invalid memory alloc request" messages,
> myself. Could you show us the sections of the dump file that trigger
> those errors?
>
> regards, tom lane
>
Attachment | Content-Type | Size |
---|---|---|
d.sql | application/octet-stream | 24.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2004-01-14 08:03:24 | Re: Best practice? Web application: single PostgreSQL user vs. multiple users |
Previous Message | Chris Travers | 2004-01-14 07:45:38 | Re: Nested transaction workaround? |