>> I'm wondering whether this truncation should be yet another available >> command? Hmmm... maybe not. > > Currently TRUNCATE pgbench_accounts command is executed within a > transaction started immediately before it. If we move it out of the > transaction, the table data will be truncated even if the copying data > failed. Maybe we can do TRUNCATE pgbench_accounts, pgbench_history > instead. Thought?
Keep the truncate in the transaction, and truncate both (or all?) tables together.