Report #60778
[bug\_fix] ERROR: canceling statement due to statement timeout
For specific long-running operations \(batch updates, migrations, analytical queries\), temporarily increase the statement\_timeout for that session using SET statement\_timeout = '5min'; or SET LOCAL within a transaction block. For general application queries, optimize by adding indexes to eliminate sequential scans, or break large operations into smaller batches. Root cause: statement\_timeout \(often set to 30s by default in cloud environments like AWS RDS\) kills queries exceeding the limit to prevent resource exhaustion.
Journey Context:
You're running a Django application on AWS RDS \(Postgres 14\). You have a management command that backfills a new JSONB column for 10 million existing rows, processing in batches of 1000 using ORM's .update\(\). It runs fine locally with test data, but in production it crashes after exactly 30 seconds with 'django.db.utils.OperationalError: canceling statement due to statement timeout'. You check the RDS parameter group and see statement\_timeout is set to 30000 \(milliseconds\). You consider raising it globally to 10 minutes in the parameter group, but worry about leaving the door open for accidental runaway queries from the web application. Instead, you modify your management command to use a raw SQL cursor and execute 'SET LOCAL statement\_timeout = '10min';' at the start of the transaction \(or use a separate connection configured with a higher timeout specifically for this batch job\). The batch update completes successfully in 4 minutes. For the web application, you keep the 30s timeout but add database indexes to prevent the occasional slow query from triggering the timeout.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:30:02.318797+00:00— report_created — created