Getting Started

Install PostRESP, verify RESP on :6379, then connect with redis-cli or any Redis client.

Choose an install path first. After PostRESP is running, verify the connection with redis-cli before wiring up an application client.

Install and verify

Choose an install path

Use Docker for the fastest local setup, or install the Postgres extensions when you already run PostgreSQL and only want the Redis-facing bits.

Run locally with Docker

Best for evaluation, local development, and quick testing. Postgres and the in-process RESP gateway ship in one image.

Install Postgres extensions

Use this when you want a persistent host install into an existing PostgreSQL database.

Recommended: verify with redis-cli

This is the fastest shared validation path after either install option — it confirms the RESP endpoint before you add application drivers. If you already know your target workflow, you can skip ahead to a client quick start.

redis-cli Quick Start

Ping the gateway, SET/GET a key, and peek at SQL storage in schema pgresp.

What you get

PostRESP makes PostgreSQL speak Redis RESP. Install the extensions, preload the gateway host, and Redis clients talk to Postgres — storage and protocol in one process.

Piece	Role
`pg_resp`	SQL storage — schema `pgresp`
`pg_resp_gw_host`	In-process RESP listener inside Postgres
Standalone `redis_gateway`	Same protocol core as a separate process (optional)

Default ports in the Docker image:

Port	Protocol	What
6379	Redis (RESP)	Client endpoint
5432	PostgreSQL	SQL / ops

Start here

If you’re new to PostRESP, use this order:

Docker Quick Start — fastest local install
redis-cli Quick Start — verify connectivity and first commands
Connect from your app — point any Redis client at :6379
Postgres extensions — when you need a host install instead of Docker

Verify your setup

Before moving on to application code, confirm PostRESP is reachable:

docker ps --filter "name=pg_resp"

redis-cli -p 6379 PING
# PONG

redis-cli -p 6379 SET hello world
redis-cli -p 6379 GET hello
# world

For a fuller walkthrough, use the redis-cli Quick Start. Driver-shaped examples live under Connect from your app.

Troubleshooting

If setup does not work on the first try:

Confirm the container is running and ports 6379 / 5432 are published with docker ps.
Inspect startup errors with docker logs pg_resp.
If 6379 is already taken on the host, map another port (-p 5762:6379) and pass -p 5762 to redis-cli.
For extension installs, confirm shared_preload_libraries includes pg_cron,pg_resp_gw_host,pg_prewarm and that you restarted Postgres after changing it.
Check Configuration for env/JSON overrides and Storage modes for durability trade-offs.

Explore next

Architecture

How storage, the RESP gateway, and deployment shapes fit together.

Commands

Full command support matrix.

Storage modes

Unlogged or logged durability.

Benchmarks

Throughput vs Valkey across durability modes.