Re: pg_restore error

I have had some problems with this in the past too, but the good news is
that after you do that, later dump restores tend to go much more smoothly as
the internal ordering will then match the (successful) load order used.
Dumping and restoring databases under development can be a real chore, but a
stable production system should be relatively OK. Just my experience anyway.

regards
Iain

----- Original Message -----
From: "Lee Wu" <Lwu(at)mxlogic(dot)com>
To: "Düster Horst" <Horst(dot)Duester(at)bd(dot)so(dot)ch>; <pgsql-admin(at)postgresql(dot)org>
Sent: Saturday, October 30, 2004 1:39 AM
Subject: Re: [ADMIN] pg_restore error

>I had the problem in 7.3.2. Postgres pg_restore reied to restore views
>before tables. I had to use -l to generate a dump list and
> change the order of restore manually and restore with -L
>
>
> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org
> [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Düster Horst
> Sent: Friday, October 29, 2004 7:52 AM
> To: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] pg_restore error
>
> OK, the manual talk about this solution, but I do have more than 2000
> objects in my DB. What is the reason that pg_dump/pg_restore are not able
> to
> create an correct order ob DB objects with respect to their constraints.
> All
> tables must be created before the views are created and so on?
>
> Horst
>
> -----Ursprüngliche Nachricht-----
> Von: Janko Richter [mailto:jankorichter(at)yahoo(dot)de]
> Gesendet am: Freitag, 29. Oktober 2004 13:14
> An: Düster Horst; pgsql-admin(at)postgresql(dot)org
> Betreff: Re: pg_restore error
>
> Hi,
>
> Try "pg_restore -l" to generate a TOC.
> You may rearrange the TOC file.
> Then use "pg_restore -L".
>
> Hope it helps,
> Janko Richter
>
>
> Düster Horst wrote:
>> Vishal
>>
>> Thank you for your answer. My problem is, I have to restore BLOBS. The
>> documentation says, it's only possible to restore blobs with pg_restore
>> in
>> one part. The way you suppose does not work with BLOBS because the
>> restauration of single objects will not restore BOLBS.
>>
>> Horst Düster
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Vishal Kashyap @ [Sai Hertz And Control Systems]
>> [mailto:vishalonlist(at)gmail(dot)com]
>> Gesendet am: Freitag, 29. Oktober 2004 11:33
>> An: Düster Horst
>> Cc: pgsql-admin(at)postgresql(dot)org
>> Betreff: Re: [ADMIN] pg_restore error
>>
>> Hi
>>
>>
>>>I thought, that pg_restore will organize the restore-prozess in an
>>>optimal
>>>order. This seems not work correct!!?? I would be grateful to hear any
>>>hints.
>>
>>
>>
>> pg_restore does not priortize till now idealy it must be like
>> restoring the functions >> tables >> views >> seqences so on...
>>
>> This is in the todo
>>
>> http://developer.postgresql.org/todo.php
>>
>> but for mean while you would have to use pg_restore to restore the
>> tables one by one and then let other thing go on.
>>
>> moreover if your database is not to large its best to make a text file
>> of the dump and run it through psql
>>
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)