Previously execute_batch always used the hardcoded 30s default timeout, ignoring the user's query_timeout_secs connection setting. This caused long-running ALTER TABLE statements on large tables to time out even when the user configured a longer timeout or disabled it entirely.