From: Adam Radłowski <adamr@informatyka.gdansk.pl>
To: Jessica Richard <rjessil@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Problem restoring with pg_dump
Date: Wed, 29 Nov 2006 00:48:56 +0100
Message-ID: <456CCAE8.30303@informatyka.gdansk.pl> (raw)
In-Reply-To: <20061128133843.36651.qmail@web58315.mail.re3.yahoo.com>
References: <20061128133843.36651.qmail@web58315.mail.re3.yahoo.com>
I'm sorry, but I have experiences only with LATNI2 and WIN1250 databases
on PostgreSQL 8.0.3, 8.0.6, 8.0.7, 8.1.3 .
I'm afraid, that without having Your SQL script file Your problem can be
difficult to resolve.
Adam
Jessica Richard wrote:
> can you please be more specific?
>
> I used pg_dump db to dump the 8.0.8 unicode db, and used
> psql db < dbdump to load the db to 8.1.4 server (on this version unicode
> becomes utf8) and got the error:
>
> ERROR: invalid byte sequence for encoding "UTF8": 0x92
>
> thanks
>
> */Adam Radlowski <adamr@informatyka.gdansk.pl>/* wrote:
>
> I had problems, like that. I've omitted them using "plain" format (SQL
> script file) of dump file. I restore data from "plain" format with psql
> - using command "\i FILE". It work always. If You gzip this "plain"
> file
> - You become simillar volume of file using binary dump format.
> Greetings
> Adam
>
> Peter Wilson wrote:
>
> >I posted this to 'general' yesterday but with no luck. This is
> probably a better
> >group.
> >
> >I've just got the following message while trying to restore a
> database :
> >
> >pg_restore : [custom archiver] Dumping a specific TOC data block
> out of order is
> >not supported without ID on this input stream (fseek required).
> >
> >The command was :
> >pg_restore -L /tmp/toc --dbname=whitebeam --disable-triggers
> --username=postgres
> >/var/backups/restore-db.psql
> >
> >/tmp/toc is a re-orderd output from :
> >
> >pg_restore -l -a /var/backups/restore-db.psql > /tmp/toc
> >
> >Using Postgres 8.1.4 on
> >Linux version 2.6.15-1.2054_FC5
> >
> >The dump itself was made on another machine running 8.1.4 on
> Fedora core 4.
> >
> >I've run similar commands on this machine before with no problems.
> Not sure why
> >I should start to have these problems now?
> >
> >Anyone else seen anything similar? Thoughts much appreciated!
> >
> >Pete
> >
> >---------------------------(end of
> broadcast)---------------------------
> >TIP 1: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo@postgresql.org so that your
> > message can get through to the mailing list cleanly
> >
> >
> >
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
>
> ------------------------------------------------------------------------
> Check out the all-new Yahoo! Mail beta
> <http://us.rd.yahoo.com/evt=43257/*http://advision.webevents.yahoo.com/mailbeta;
> - Fire up a more powerful email and get things done faster.
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: adamr@informatyka.gdansk.pl, rjessil@yahoo.com
Subject: Re: Problem restoring with pg_dump
In-Reply-To: <456CCAE8.30303@informatyka.gdansk.pl>
References: <20061128133843.36651.qmail@web58315.mail.re3.yahoo.com> <456CCAE8.30303@informatyka.gdansk.pl>
* 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