Skip to content
PostRESP
Esc
navigateopen⌘Jpreview
On this page

Introduction

PostRESP — PostgreSQL that speaks Redis (Redis/Valkey-compatible RESP), storage and protocol co-located in one process.

For the product pitch (self-hosters, small teams, compose-file story), see the marketing home. This page is the operator docs entry point.

Install the extensions, preload the gateway host, and Redis clients talk RESP to Postgres — storage and protocol in one process. The same gateway can also run as a standalone service next to Postgres when you need that deployment shape.

# Preferred: everything inside PostgreSQL
redis-cli :6379 → in-process RESP gateway → pgresp.* SQL → Postgres

# Also supported: gateway as an external service
redis-cli :6379 → standalone redis_gateway → same pgresp.* SQL → Postgres

Product goal: CREATE EXTENSION (+ preload) and you’re speaking Redis — no separate app tier required for the common case.

What you get

Piece Role
pg_resp SQL storage extension — schema pgresp
pg_resp_gw_host In-process RESP listener inside Postgres (primary path)
pg_cron Schedules active TTL deletion so expired keys are cleaned up in the background
pg_prewarm Reloads recently used pgresp.* data into memory after a Postgres restart
Standalone redis_gateway Same protocol core, run as a separate process when useful

Keys live in schema pgresp. Product extension names remain pg_resp / pg_resp_gw_host. Docker enables pg_cron and pg_prewarm by default — see Commands › TTL and Buffer cache prewarm.

Next steps

Was this page helpful?