TDSQL-C for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Suggestions on Usage Specifications
- Kernel Features
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Value-Added Services Billing Overview
- Database Audit
- Audit Rule Template
- Serverless Service
- Serverless Introduction
- Serverless Resource Pack
- Configuration Change
- Operation Guide
- Database Connection
- Configuring Network Address
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Kernel Features
- Managing Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Console Account
- Database Account
- Configuring Custom Password Strength
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Utilization of Columnar Storage Indexes
- Read-Only Analysis Engine
- Feature Limits and Compatibility
- Description of Functions and Operators
- Read-Only Analysis Engine Management
- Data Loading
- Executing Queries
- Exclusive Features
- Performance Optimization
- Performance White Paper
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Performing Backup
- Managing Backup
- Rollback
- Restoring Data from Logical Backups
- Restoring Data Through the Console
- Restoring Data from Snapshot Backup
- Data Migration
- Parallel Query
- Setting Parallel Query
- Database Security and Encryption
- Access and Authorization
- Security Group Management
- TencentDB Security Group Management
- Monitoring and Alarms
- Monitoring
- Alarms
- Monitoring Metric Alarm
- Practical Tutorial
- Data Rollback
- Database/Table-Level Rollback
- Rolling back Entire Cluster
- White Paper
- Security White Paper
- Performance White Paper
- Troubleshooting
- Connection Issues
- API Documentation
- Making API Requests
- Instance APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
DocumentationTDSQL-C for MySQLOperation GuideRead-Only Analysis EngineExclusive FeaturesOrdered Pagination Feature
Ordered Pagination Feature
Last updated: 2025-03-20 16:01:44
The ordered pagination feature of the read-only analysis engine can solve the problem of unstable pagination query results caused by duplicate field values of the order by clause during parallel data queries. This document describes how to use the ordered pagination feature. For a detailed feature introduction, see Paging Order Preservation Capability.
Ordered Pagination Scenarios
Only the limit operator is used, and no order by operator is used.
Duplicate order by keys exist, and only some fields in the output result are sorted.
The subquery involves sorting, but sorting is not performed in the outer query.
Usage Instructions
Enable the ordered pagination feature globally.
Use the feature of setting instance parameters to modify the parameter libra_preserve_order_for_pagination of the read-only analysis engine. The default value of this parameter is OFF. You can set the value to ON to enable the ordered pagination feature for the entire instance.
Note:
The ordered pagination feature performs implicit sorting on the output results of queries by default. Therefore, it may cause performance degradation in scenarios with large result sets. It is recommended to specify to use the ordered pagination feature in SQL statements that require this feature.
Enable the ordered pagination feature in a session.
Specify session-level parameters after you log in to the read-only analysis engine to enable/disable the ordered pagination feature in the current session.
mysql> set libra_preserve_order_for_pagination=on;mysql> set libra_preserve_order_for_pagination=off;
Specify to use the ordered pagination feature during SQL execution.
When a SQL statement is executed, add a hint to specify this SQL statement to use the ordered pagination feature.
Note:
If you use the MySQL client to access the read-only analysis engine, add the -c parameter. Otherwise, the settings of using the ordered pagination feature during SQL execution cannot take effect.
mysql> select /*+ SET_VAR(libra_preserve_order_for_pagination=ON) */ t1.c1, t1.c2 from t1, t2 where t1.c1 = t2.c1 order by t1.c1 limit 10,10;
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No