Input SQL to Optimize

A workload is the SQL you want to optimize: a single DML statement or multiple statements separated by ;. PawSQL supports the following sources for SQL input.

Goal

Input SQL to optimize from a text box, a SQL file, database logs, or a MyBatis Mapper file to build the task workload.

Prerequisites

A workspace is available.
The workspace engine, version, and schema match the target SQL.
Referenced tables, views, and columns exist in the workspace.
SQL has no embedded credentials or sensitive data.

Input sources

PawSQL supports several SQL input sources; choose the one that matches your workflow.

SQL text
SQL file
Slow query log
MyBatis Mapper file

Paste or type valid SQL in the text box. Multiple statements can be separated by ;. Best for ad hoc analysis or a single problematic statement.

Upload a SQL file. PawSQL extracts the statements, with multiple statements separated by ;.

Extract SQL from a database slow log or general log.MySQLThe slow log records statements whose execution time reaches long_query_time (seconds) and rows examined reach min_examined_row_limit; enable log_queries_not_using_indexes to also record queries that do not use an index; the general log records every statement executed during a client session.

set global log_output='file';
set global slow_query_log='on';
set global slow_query_log_file = '/tmp/localhost-slow.log';
set global long_query_time = 5;

PostgreSQLEnable SQL logging in postgresql.conf, and use log_min_duration_statement (milliseconds) to record only slow statements:

log_statement = 'all'
log_directory = 'pg_log'
log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log'
logging_collector = on
log_min_duration_statement = 5000

openGaussConfigured like PostgreSQL, via log_statement and log_min_duration_statement in postgresql.conf.

Enter SQL to optimize in the SQL editor — Input SQL to optimize from text, a file, logs, or a Mapper file

Supported SQL types

select, update, delete, insert ... select, merge, replace.

Parameters and sanitization

Use a placeholder syntax supported by the current PawSQL release, and provide representative values when needed;
parameter values affect selectivity and execution plans, so performance validation should cover common and boundary scenarios;
replace sensitive literals with safe representative values;
convert a template SQL that cannot be parsed into a representative executable statement.

Troubleshooting

Symptom	Check first
Parsing fails	Dialect, version, statement completeness, placeholders, delimiters
Object unresolved	Workspace, default schema, identifier case, metadata freshness

Expected Result

The chosen source is parsed into the workload SQL that appears in the optimization task.

Verification

Confirm the SQL parses, referenced tables and columns resolve in the workspace, and no credentials or sensitive data remain.

Input SQL to Optimize

Goal

Prerequisites

Input sources

Supported SQL types

Parameters and sanitization

Troubleshooting

Expected Result

Verification

Next steps

Create and configure an optimization task

Workspaces

Read the results

​Goal

​Prerequisites

​Input sources

​Supported SQL types

​Parameters and sanitization

​Troubleshooting

​Expected Result

​Verification

​Next steps

Create and configure an optimization task

Workspaces

Read the results

Goal

Prerequisites

Input sources

Supported SQL types

Parameters and sanitization

Troubleshooting

Expected Result

Verification

Next steps