Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

PostgreSQL to SingleStore Data Type Mapping

The following mappings define how PostgreSQL data types are represented in SingleStore.

For more information about SingleStore data types, refer to Data Types.

String Types

PostgreSQL Type

SingleStore Type (more info)

CHAR

CHAR

VARCHAR(n) where n ≤ 21843

VARCHAR(n)

VARCHAR with no length, or VARCHAR(n) where n > 21843

LONGTEXT

BPCHAR

CHAR

TEXT

LONGTEXT

UUID

VARCHAR

Note: VARCHAR with no length, or with a length greater than 21,843, is mapped to LONGTEXT. This mapping applies to newly created destination tables. Destination tables created with Ingest versions earlier than 4.6.0 retain VARCHAR(21843) for these source types. CDC does not automatically change these existing columns to LONGTEXT. If a source value exceeds 21,843 characters, the load can fail. For recovery steps, refer to Flow on Helios FAQ.

Integer Types

PostgreSQL Type

SingleStore Type (more info)

SMALLINT

SMALLINT

INTEGER

INT

BIGINT

BIGINT

SMALLSERIAL

SMALLINT

SERIAL

INT

BIGSERIAL

BIGINT

BOOL / BOOLEAN

TINYINT

Floating Point Types

PostgreSQL Type

SingleStore Type (more info)

REAL

FLOAT

FLOAT4

FLOAT

FLOAT8

DOUBLE

DOUBLE PRECISION

DOUBLE

Decimal and Numeric Types

PostgreSQL Type

SingleStore Type (more info)

DECIMAL

DECIMAL

NUMERIC

DECIMAL (65,30)

MONEY

DECIMAL

Binary String Types

PostgreSQL Type

SingleStore Type (more info)

BYTEA

LONGBLOB

Date and Time Types

PostgreSQL Type

SingleStore Type (more info)

DATE

DATE

TIME

TIME(6)

TIMESTAMP

DATETIME(6)

TIMESTAMPTZ

DATETIME(6)

Invalid PostgreSQL DATETIME and TIMESTAMP Values

Certain invalid DATETIME values are automatically converted to valid SingleStore values:

PostgreSQL Type

SingleStore Type

0000-00-00 00:00:00

1000-01-01 00:00:00

0001-00-00 00:00:00

1001-01-01 00:00:00

0001-01-01 01:01:01

1001-01-01 01:01:01

0025-01-01 00:00:00

1025-01-01 00:00:00

For TIMESTAMP, the following conversion takes place:

PostgreSQL Type

SingleStore Type

0000-00-00 00:00:00

1000-01-01 00:00:00

Flow converts these invalid values using the following rules, in order:

  1. Zero dates

    If the value is 0000-00-00 00:00:00, convert it to 1000-01-01 00:00:00.

  2. Years below 1000

    If the year is between 0000 and 0999, add 1000 to the year.

    Examples:

    • Year 0001 becomes 1001

    • Year 0025 becomes 1025

    • Year 0999 becomes 1999

  3. Invalid month or day (00)

    If the month or day is 00, it is replaced with 01.

    • If month is 00, replace it with 01.

    • If day is 00, replace it with 01.

    For example:

    • 0001-00-00 → (Rule 2) → 1001-00-00 → (Rule 3) → 1001-01-01

These rules ensure that common invalid values can be ingested without pipeline failures while preserving their relative ordering as much as possible.

JSON Types

PostgreSQL Type

SingleStore Type (more info)

JSON

JSON

JSONB

JSON

Additional Notes

  • TIME is mapped to TIME(6).

  • TIMESTAMP and TIMESTAMPTZ types are mapped to DATETIME(6). 

Last modified:

Was this article helpful?