Amazon Redshift

Connect to Redshift clusters and Serverless over the PostgreSQL wire protocol, with DISTKEY and SORTKEY metadata display

Amazon Redshift Connections

TablePro connects to Amazon Redshift using the same libpq driver as PostgreSQL, plus Redshift-specific metadata queries for distribution style, sort keys, and table size. The PostgreSQL page applies unless noted here.

Connection Settings

Field	Default	Notes
Host	-	Cluster endpoint, e.g. my-cluster.abc123xyz.us-east-1.redshift.amazonaws.com
Port	5439
Database	dev	Required; every cluster has a dev database

Fill in the form and click Save & Connect. Connection URLs use the redshift:// scheme, see Connection URL Reference.

AWS IAM authentication is not available for Redshift connections (unlike MySQL and PostgreSQL). Use the cluster’s database username and password.

Features

Schemas: like PostgreSQL, default schema public. Table metadata comes from svv_table_info: distribution style, sort keys, and table size.

DDL: table definitions include DISTKEY, SORTKEY, DISTSTYLE, and ENCODE directives. Foreign keys display as informational; Redshift does not enforce them.

Distribution style and sort keys in table info

Backup & Maintenance: Backup Dump and Restore Dump (via pg_dump) work for Redshift, and the maintenance panel offers VACUUM with FULL, ANALYZE, and VERBOSE options. See Backup & Restore.

Import & Export: export to CSV, JSON, SQL, or XLSX. Import from CSV, JSON, or SQL. See Import & Export.

Structure Editing

TablePro disables the structure-editing UI for Redshift: no column, index, or key changes from the structure tab. Run ALTER TABLE statements in the SQL editor instead.

Redshift Limitations

Columnar warehouse, not a general-purpose RDBMS: no traditional indexes (DISTKEY/SORTKEY instead), no enums, sequences, or triggers, and foreign keys are informational only.

Troubleshooting

Connection refused: check the security group allows port 5439, the cluster is publicly accessible (or use an SSH tunnel), and the cluster is not paused.

Auth failed: verify the master username and password in the AWS Console.

Slow queries: check distribution with SELECT * FROM svv_table_info WHERE "table" = 'your_table', run ANALYZE to update stats, and match SORTKEY to your WHERE/JOIN predicates.