Trino safe mode and review
How Tablyne limits Trino runs, estimates reads, classifies statements and asks for confirmation on production and read-only connections.
Trino connections start in the safe mode that confirms writes. Tablyne classifies each statement in Rust before it sends anything, and that includes the SQL behind an EXECUTE.
Limits per run
Three limits can be set on the connection: maximum execution time, maximum total time and maximum physical scan in MiB. Tablyne sends them as session properties with every request. A SET SESSION in a tab cannot loosen them, because the stricter value wins, and the screen shows the limit that applies. If the server refuses a property, the run fails with the reason. You can then choose to run without that limit. Tablyne never drops it silently. On a production connection, running without a limit asks for another confirmation.
Estimate before a read
The estimate runs EXPLAIN (TYPE IO), which does not run the query. You can set it to never, always or only in production. When it is on, you see the estimated output size and rows and confirm before the read starts. If the connector reports no statistics, you see “Estimate unavailable”.
Writes
A batch that changes data or structure is reviewed. On a production connection it also asks for confirmation, and the message says there is no transaction to roll back. A confirmation is tied to the exact text, parameters and limits, and it expires after five minutes.
Read-only connections
A read-only connection rejects writes before they are sent. The form notes that this is a Tablyne safeguard, so you should also use access rules on the server.
Ending queries
In the Activity view you can end your own queries after a confirmation. Queries of other users can be listed but not ended. Read-only connections cannot end queries.