Syntax

TRUNCATE [TABLE] <table_name>;

Remarks

• SingleStore supports online TRUNCATE, which means that you can read and write while the table is being truncated. For Rowstore tables, TRUNCATE is the preferred method (vs DELETE).

• Blocking: Note that online TRUNCATE will not begin truncating the table, but it will wait until all DML queries that were already running on the table finish. This allows any in-progress queries to complete execution before truncating the table, and ensures consistency of results from queries on the table since the time of execution of TRUNCATE. New read or write queries are blocked until the in-progress queries are finished and TRUNCATE has begun truncating the table. This blocking period lasts until all in-progress reads and writes have completed. TRUNCATE blocks the table via a lock.

  If you are frequently running TRUNCATE statements on a table and have a lot of long-running queries on that table, then your normal workload may experience some periods of delay since the TRUNCATE operation blocks other queries from starting while it waits for completion of long-running queries.

  The TRUNCATE operation throws a timeout error if there are long running DML queries in your workload, which extends the blocking period to several minutes.

  Refer to ISSUE: Long Running Queries Blocking DDL Operations and Workload for resolving query timeout errors due to long running queries in a workload.

• This command can be run on the master aggregator node, or a child aggregator node (see Node Requirements for SingleStore Commands ).

• This command causes implicit commits. Refer to COMMIT for more information.

• Table memory can be freed when the TRUNCATE command is run. For information on when/how much table memory is freed when this command is run, see Memory Management.

• Refer to the Permission Matrix for the required permission.

Example

TRUNCATE TABLE table_name;

Related Topics

• DELETE