Re: Migrating from 7.1 to 7.2 using pg_dump/pg_restore fails - UNICODE error

From: "Soeren Laursen" <sl(at)scrooge(dot)dk>
To: Markus Bertheau <twanger(at)bluetwanger(dot)de>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Migrating from 7.1 to 7.2 using pg_dump/pg_restore fails - UNICODE error
Date: 2003-07-07 08:12:12
Message-ID: 3F09477C.15202.3DD58E@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ludwig Lim 2003-07-07 08:24:43 Stuck Spinlock Error Message
Previous Message Stephan Szabo 2003-07-06 23:35:15 Re: Problem when migrating my BB.DD Postgresql 7.2.3 to