On Thu, 2008-09-11 at 15:25 -0400, Andrew Dunstan wrote:
> Great, thanks (and also to Guillaume).
>
> It looks to me like the simple way around this issue would be to provide
> an option to have pg_restore emit:
> begin; truncate foo; copy foo ... commit;
>
> The truncate will be trivial as there won't be any data or indexes at
> that stage anyway.
Not sure which stage you're talking about. If this is a parallel restore
and you are running a create in one session and a load in another, then
ISTM you have no way of knowing that for certain.
-- Simon Riggs www.2ndQuadrant.comPostgreSQL Training, Services and Support
