On Fri, Sep 1, 2017 at 11:29 PM, Fabien COELHO <coe...@cri.ensmp.fr> wrote: > >>> 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.
Attached latest patch incorporated the comments I got so far. Please review it. Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
pgbench_custom_initialization_v9.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
