PlanetScale Query Exceeded Row or Time Limit

How to fix it

Try these in order — the most common fix is first.

1. 1. Batch large writes

   Copy steps
   1. Update or delete in chunks below 100k rows
   2. Loop with LIMIT and a key range
   Did this fix it? Yes No

2. 2. Use OLAP mode for big reads

   Copy steps
   1. Run SET workload = OLAP for the session
   2. Note updates and deletes keep the 100k cap
   Did this fix it? Yes No

3. 3. Add indexes

   Copy steps
   1. Run EXPLAIN on the query
   2. Add the missing index through a deploy request
   Did this fix it? Yes No

Symptoms

Errors about row limits, results larger than max message size or killed transactions.

Why it happens

• More than 100k rows returned, updated or deleted per query
• Result over 64 MiB
• Transaction longer than 20 seconds

This guide also covers

• planetscale resource_exhausted grpc message larger than max
• planetscale 100k rows limit

The same problem in other apps

All plan limits, paywalls & watermarks guides →

• Supabase Edge Function 546 WORKER_LIMIT Error (Supabase)

Other PlanetScale errors

• PlanetScale Transaction Pool Connection Limit Exceeded
• PlanetScale Foreign Key Constraints Not Working
• PlanetScale Safe Migrations: DDL Statement Rejected
• PlanetScale Prisma Connection Errors
• PlanetScale Postgres Import Fails or Is Slow
• PlanetScale Postgres Extension Not Available
• PlanetScale Unexpected Bill: Storage, Backups and Transfer
• PlanetScale Connection Errors During Outage