Postgres Pro
Downloads
Home   >   mailing lists

Re: Migrating from 7.1 to 7.2 using pg_dump/pg_restore fails - UNICODE error - Mailing list pgsql-admin

From Soeren Laursen
Subject Re: Migrating from 7.1 to 7.2 using pg_dump/pg_restore fails - UNICODE error
Date
Msg-id 3F09477C.15202.3DD58E@localhost
Whole thread Raw
In response to Re: Migrating from 7.1 to 7.2 using pg_dump/pg_restore  (Markus Bertheau <twanger@bluetwanger.de>)
Responses Re: Migrating from 7.1 to 7.2 using
List pgsql-admin
Tree view 
It looked like that worked,

How about large objects (blobs). That is the reason I use custom
format or am I missing a point here?

I guess I might could use a lot of switches and only dump the
blobs in a single file?

Regards,

Søren,
> В Пнд, 07.07.2003, в 00:01, Soeren Laursen пишет:
> > Hi,
> >
> > I am not sure how and where I should use the \encoding latin1
> >
> > Something like,
> >
> > psql test01
> > \encodinng latin1
> > \q
> >
> > pg_restore .....
>
> Ah. Load the backup in a non-unicode database, dump it using the text
> format (i.e. not the custom format), put the encoding thing in front of
> the file and load it into your unicode database.
>
> --
> Markus Bertheau.
> Berlin, Berlin.
> Germany.

pgsql-admin by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Problem when migrating my BB.DD Postgresql 7.2.3 to
Next
From: Ludwig Lim
Date:
Subject: Stuck Spinlock Error Message