Sequelize Query Cancellation Across Dialects Lacks Unified Timeout Configuration

Determine whether a single Sequelize configuration can both abort an in‑flight query at the database level and ensure the transaction is rolled back and the connection returned to the pool across PostgreSQL, MySQL/MariaDB, and SQL Server.

Pool.acquire only limits waiting for a connection; after checkout the query continues under the driver; PostgreSQL provides statement_timeout but other dialects expose separate timeout fields, and the documented pool options do not cover query cancellation.

Which dialect‑specific timeout option should be used for each driver to achieve consistent cancellation? Does the chosen timeout guarantee transaction rollback and connection reuse, or must additional error handling be applied? Is there a version‑stable API that abstracts this behavior?