Skip to main content
Use FLUSHALL to delete every key in every database. Upstash exposes a single logical database, so FLUSHALL and FLUSHDB have the same effect here. ASYNC frees the memory in a background thread, which returns faster on large datasets, while SYNC frees it before replying. The deletion is immediate and irreversible: there is no confirmation step and nothing to undo. Keep it out of application code, run it only against disposable databases, and require an explicit operator action wherever tooling exposes it.

Syntax

Arguments

Important points

  • This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
  • This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
  • This deletes the database contents. Test against a disposable database and require an explicit operator action in production tooling.

Response

The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.

Examples

TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.