Andrew Dunstan wrote:
The pg_dump output was never backward compatible. (The input is.) So the output of parallel restore need not be backward compatible either. (Unless this mandate has changed dramatically while I was not looking?) So always issue TRUNCATE ONLY, if that is what the logic requires. The additional benefit is that this will fail safely on older versions.
No it won't fail safely on older versions, because the truncate is part of a transaction, and thus the data member(s) will all fail.
I meant "safe" as in, it won't randomly delete more data than you intended. I didn't mean in as in do-what-I-mean. :-)
I'd like to be able to use 8.4 pg_restore to run parallel restores on older servers, and the fix for this is utterly trivial. I'll be posting a new patch with it in today.
Works for me. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
