Re: pg_restore and FK constraints with large dbs

--- Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> wrote:
> Only assuming that no changes were made between dump and restore. This
> could be changes to schema or data done manually, but it could also be a
> locale or possibly encoding change if you have any textual foreign keys.

I'm restoring the database, meaning that (a) it's believed that current db is
corrupt and needs to be restored or (b) the db is moved to a different server.
Hence any changes after the last dump will be blown away anyway, wouldn't they?
One would have to apply the changes manually or whatever, once the restore is
completed.

The problem is that restoration process is taking too long, mostly due to FK
checks, as it was described earlier, and it appears there's no way to speed
this up.

Sadly, I'm looking at m*Sql and see that they have "SET FOREIGN_KEY_CHECKS=0"
command.

Thanks

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree