[Pkg-postgresql-public] Bug#859033: pg_dump: creates dumps that cannot be restored

Thorsten Glaser t.glaser at tarent.de
Wed Mar 29 19:18:39 UTC 2017


Dixi quod…

> ‣‣‣ What have I expected?
> 
> That pg_dump recognises the dependency (there i̲s̲ a FOREIGN KEY reference
> in there) and reorders the tables dumped.

I’d actually be happy if there were a way to restore those dumps,
for example by temporarily disabling constraint checks during the
restore. This MUST NOT cost consistence though — constraint checks
would, in this restore mode, need to be re-enabled AND all data
checked against them BEFORE the --single-transaction surrounding
all this finishes, and abort it if any data fails the constraints.

Well, actually even happier as it would allow me to restore such
dumps created by those buggy pg_dump versions, which are abundant.

Thanks in advance,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg



More information about the Pkg-postgresql-public mailing list