Use FLUSHDB to delete every key in the current database.
Since Upstash exposes a single logical database, this removes everything, exactly like FLUSHALL. ASYNC frees the memory in a background thread and SYNC frees it before replying.
The deletion is immediate and irreversible. It is a convenient way to reset a test database between runs, and it should never be reachable from application code that runs against production data.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
(ASYNC | SYNC) | No | No | Choose one form: ASYNC (request asynchronous cleanup); SYNC (request synchronous cleanup). |
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.
| Protocol | Reply |
|---|---|
| RESP2 | Simple string OK |
| RESP3 | Simple string OK |
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.