firebird wire protocol
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8. Batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic response — where Object id is the array handle. Chapter 7. Arrays 26 Chapter 8. Batches Statement batches were introduced in protocol v16 (Firebird 4.0). 8.1. Create Client Int32 Operation values (formatted message repeats 'Number of messages' times) Server Generic response Chapter 8. Batches 27 8.3. Execute batch Client Int32 Operation code (op_batch_exec) Int32 Statement handle0 码力 | 40 页 | 213.15 KB | 1 年前3TiDB v6.1 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3869 15.3.13 Does TiDB statement. • For performance considerations, see Performance Considerations. • In scenarios where large batches of data need to be deleted, Non-Transactional bulk- delete can significantly improve performance {batch_size} {delete_statement}; Parameter Name Description {shard_column} The column used to divide batches. {batch_size} Control the size of each batch. {delete_statement} The DELETE statement. The preceding0 码力 | 4487 页 | 84.44 MB | 1 年前3TiDB v7.6 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4881 15.3.13 Does TiDB splits the restore task into a large num- ber of small tasks and scatters them to all TiKV nodes in batches. The new parallel recovery algorithm fully utilizes the resources of each TiKV node, thereby achieving statement. • For performance considerations, see Performance Considerations. • In scenarios where large batches of data need to be deleted, Non-Transactional bulk- delete can significantly improve performance0 码力 | 6123 页 | 107.24 MB | 1 年前3TiDB v6.5 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4401 15.3.13 Does TiDB statement. • For performance considerations, see Performance Considerations. • In scenarios where large batches of data need to be deleted, Non-Transactional bulk- delete can significantly improve performance {batch_size} {delete_statement}; Parameter Name Description {shard_column} The column used to divide batches. {batch_size} Control the size of each batch. {delete_statement} The DELETE statement. The preceding0 码力 | 5282 页 | 99.69 MB | 1 年前3TiDB v7.5 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4809 15.3.13 Does TiDB statement. • For performance considerations, see Performance Considerations. • In scenarios where large batches of data need to be deleted, Non-Transactional bulk- delete can significantly improve performance {batch_size} {delete_statement}; Parameter Name Description {shard_column} The column used to divide batches. {batch_size} Control the size of each batch. {delete_statement} The DELETE statement. The preceding0 码力 | 6020 页 | 106.82 MB | 1 年前3TiDB v7.1 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4638 15.3.13 Does TiDB statement. • For performance considerations, see Performance Considerations. • In scenarios where large batches of data need to be deleted, Non-Transactional bulk- delete can significantly improve performance {batch_size} {delete_statement}; Parameter Name Description {shard_column} The column used to divide batches. {batch_size} Control the size of each batch. {delete_statement} The DELETE statement. The preceding0 码力 | 5716 页 | 104.74 MB | 1 年前3TiDB v5.3 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2530 13.2.9 Does TiDB interval �→ Newly added Determines the interval at which Raft messages are sent in batches. The Raft messages in batches are sent at every interval specified by this configu- ration item. When the value Follower Proxy and modifying the batch waiting time required when the PD client requests TSO in batches. This helps improve the overall scalability of the system. 43 – Support enabling or disabling PD0 码力 | 2996 页 | 49.30 MB | 1 年前3TiDB v8.3 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 5181 15.3.13 Does TiDB usually first stores the complete result set in memory, and then returns the data to the client in batches. If the result set is too large, TiDB might temporarily write the result to the hard disk. Starting statement. • For performance considerations, see Performance Considerations. • In scenarios where large batches of data need to be deleted, Non-Transactional bulk- delete can significantly improve performance0 码力 | 6606 页 | 109.48 MB | 9 月前3TiDB v8.5 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 5254 15.3.13 Does TiDB TSO from PD, TiDB collects multiple TSO requests during a specific period and processes them in batches serially to decrease the number of Remote Procedure Call (RPC) requests and reduce PD workload. In avoid the TiKV OOM issues caused by uneven distri- bution of regions during fast table cre- ation in batches. 59 Variable name Change type Description tidb_ �→ schema �→ _ �→ cache �→ _ �→ size Modified0 码力 | 6730 页 | 111.36 MB | 9 月前3TiDB v8.4 Documentation
ment count 5001 exceeds the transaction limitation while using Sqoop to write data into TiDB in batches · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 5233 15.3.13 Does TiDB TSO from PD, TiDB collects multiple TSO requests during a specific period and processes them in batches serially to decrease the number of Remote Procedure Call (RPC) requests and reduce PD workload. In avoid the TiKV OOM issues caused by uneven distri- bution of regions during fast table cre- ation in batches. 54 Variable name Change type Description tidb_ �→ schema �→ _ �→ cache �→ _ �→ size Modified0 码力 | 6705 页 | 110.86 MB | 9 月前3
共 99 条
- 1
- 2
- 3
- 4
- 5
- 6
- 10