Re: [GENERAL] Disabling and enabling constraints and triggers to make pg_restore work

"Ken Winter" <[EMAIL PROTECTED]> writes: > ... > So, the process I have in mind goes like this: > ... > 3. At the end of the release cycle, empty all the data from the development > instance, shut down the production instance (or at least write-lock up its > data), and copy the production data (dat

Re: [GENERAL] Disabling and enabling constraints and triggers to make pg_restore work

Cc: PostgreSQL pg-general List Subject: Re: [GENERAL] Disabling and enabling constraints and triggers to make pg_restore work "Ken Winter" <[EMAIL PROTECTED]> writes: > I'm trying to do a data-only pg_restore. I'm running into a roadblock > whe

Re: [GENERAL] Disabling and enabling constraints and triggers to make pg_restore work

"Ken Winter" <[EMAIL PROTECTED]> writes: > I’m trying to do a data-only pg_restore. I’m running into a roadblock > whenever the restore tries to populate a table with a foreign key before it > has populated the primary key table that it refers to: This violates the FK > constraint, which aborts th

[GENERAL] Disabling and enabling constraints and triggers to make pg_restore work

I’m trying to do a data-only pg_restore. I’m running into a roadblock whenever the restore tries to populate a table with a foreign key before it has populated the primary key table that it refers to: This violates the FK constraint, which aborts the restore. Given the complexity of the database