| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Ralf Schuchardt *EXTERN*" <rasc(at)gmx(dot)de>, Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
| Cc: | "General, Postgres" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: inconsistent backup? |
| Date: | 2013-12-20 08:27:24 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17C855F4@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ralf Schuchardt wrote:
> Am 19.Dez. 2013 um 09:41 schrieb Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>:
>> don't ask why, but a customer created tables with foreign key constraints but
>> with inconsistent data.
>>
>> Because of this he disabled all triggers (alter table foo disable trigger all).
>> So far, so bad ...
>> (he can't clean the data at the moment)
>>
>> In the dump there are the constraints, but NOT the disable triggers. In other
> > words: no way to restore.
>>
>> What can we do now?
>
> pg_restore has a --disable-triggers option, that could be of some help. Or you add the command to the
> top of the sql dump file.
... or you can edit the dump and change the necessary DDL statements.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arindam Mondal | 2013-12-20 09:08:13 | connect using quirrel sql client |
| Previous Message | Michael Paquier | 2013-12-20 07:01:16 | Re: Best way to sync possibly corrupted data? |