Many of our customers have a variety of data sets with different data types coming from different sources. Here at, we replicate your data from Amazon RDS to Amazon Redshift in near real-time, but unfortunately, we cannot support all of the source data types due to the current limitations of Amazon Redshift. For a table or column to successfully replicate from the source to the target, your data structure must adhere to the supported Amazon Redshift data types.

Below is a quick reference of the currently supported data types in Amazon Redshift:

Data type Aliases Description
SMALLINT INT2 Signed two-byte integer
INTEGER INT, INT4 Signed four-byte integer
BIGINT INT8 Signed eight-byte integer
DECIMAL NUMERIC Exact numeric of selectable precision
REAL FLOAT4 Single precision floating-point number
DOUBLE PRECISION FLOAT8, FLOAT Double precision floating-point number
BOOLEAN BOOL Logical Boolean (true/false)
CHAR CHARACTER, NCHAR, BPCHAR Fixed-length character string
VARCHAR CHARACTER VARYING, NVARCHAR, TEXT Variable-length character string with a user-defined limit
DATE Calendar date (year, month, day)
TIMESTAMP TIMESTAMP WITHOUT TIME ZONE Date and time (without time zone)
TIMESTAMPTZ TIMESTAMP WITH TIME ZONE Date and time (with time zone)
We'll handle your ETL pipeline.

We are confident as Amazon Redshift matures more data types will be supported, however at this time only the above data types are supported. Any tables and/or columns which do not adhere to this structure, unfortunately, will not be replicated. While there are ways to work around this, we suggest as a best practice to structure your data to match the currently supported data types in Amazon Redshift.