Amazon Redshift
Amazon Redshift with pREST — PostgreSQL-based warehouse connectivity with important dialect differences and a cautious support matrix.
Last updated
Amazon Redshift with pREST — PostgreSQL-based warehouse connectivity with important dialect differences and a cautious support matrix.
Amazon Redshift is PostgreSQL-based but not full PostgreSQL. pREST can connect using the PostgreSQL driver path with vendor-required parameters. Label: Compatible with caveats.
Last updated: July 11, 2026 · Label: Compatible with caveats
Also see: Integrations — Amazon Redshift.
Connection
partial — requires Redshift-compatible URL options
Schema discovery
partial — validate against your cluster
CRUD
partial — prefer read-heavy / controlled writes; warehouse semantics differ
Filtering / ordering / pagination
partial — SQL differences vs PostgreSQL
Transactions
partial — Redshift transaction model differs
Scripts (/_QUERIES)
preferred path for Redshift-safe SQL
MCP (/_mcp)
partial — use read-only roles; verify tools against catalog
ACL / permissions
supported at pREST layer; also enforce IAM/DB grants
Use a PostgreSQL-style URL with Redshift’s OpenSourceSubProtocolOverride (see AWS docs on Redshift vs PostgreSQL):
export PREST_VERSION=2
export DATABASE_URL='postgresql://user:pass@redshift-endpoint:5439/dev?OpenSourceSubProtocolOverride=true'Use PREST_PG_SSL_* for TLS. See Upgrading to v2 for SSL env naming.
Treat Redshift primarily as analytics / read access through pREST.
Prefer custom queries over assuming PostgreSQL CRUD parity.
For AI agents, use read-only credentials and MCP over HTTP.
Support labels and roadmap: Databases.
Also see the shorter integration note: Integrations — Amazon Redshift.
Important SQL and type differences vs PostgreSQL — read AWS: Redshift and PostgreSQL.
Not a substitute for a transactional OLTP PostgreSQL deployment.
Do not assume every pREST filter operator maps cleanly; test before production.
Roadmap (analytical read-only track)
Last updated