"Nick Fankhauser" <[EMAIL PROTECTED]> writes:
>> There are a lot of situations where pg_dump fails to pick a safe reload
>> order at the moment (that's why pg_restore has that wild and woolly set
>> of options for manual adjustment of the reload order).
> Is this considered a bug, or a generally a
> You could check this by running pg_restore with query logging
> turned on, to see what commands it's actually issuing -- or just do
> "pg_restore -s" into a text file and eyeball the generated script.
I did this, and there is a view created before the table it refers to.
> There are a lot of
"Nick Fankhauser" <[EMAIL PROTECTED]> writes:
> It appears that in the process of creating the schema, pg_restore attempted
> to create an object that required the existence of actor, which wasn't
> restored yet. My conjecture is that the objects are just being created in
> the wrong order.
Probab
Hi-
Thanks for the helpful suggestions on this problem last Wednesday morning- I
spent the rest of the day in a meeting, and I'm now returning to the problem
post-holiday. I apologize for the slow response to your ideas.
Tom- You were correct, I was restoring the wrong database in my example with
Hi-
I'm trying to do a dump & restore of a complete database using tar archive
format. I've previously used the text dump approach, so I'm very new to this
method.
I created the dump using:
pg_dump -Ft alpha > alpha.dump.tar
I'm trying to restore into an empty db using:
pg_restore -d alpha2
