Very likely could be foreign key references. I think MySQL may drop the foreign key references and then recreate them, but postgres does not.
I am not sure this is exactly the same as a partial restore as they mention that they drop the db and then recreate it, which should not be possible with a partial restore. Obviously seeing the logs from postgres would be useful. On Tue, Mar 22, 2011 at 9:09 AM, Knut Staring <[email protected]> wrote: > Does anyone have experience with partial/incremental restore of postgresql > dbs? > >> 3. I’m having some issues with PGadmin’s restore utility. It doesn’t seem >> to want to restore to a database which is currently active or already has >> data in it. I’ve found the workaround is to create a new db with a different >> name, restore to that, then take the other one off-line, rename it … old and >> rename the new one. That’s odd. MySQL utilities don’t seem to have a >> problem with that. This is important so that I can refresh my local copy of >> the database to work off-line. Do you have any other suggestions? > > Knut > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > -- Jason P. Pickering email: [email protected] tel:+260974901293 _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
