@kapa.ai For a postgresql table, can a field of type xid8 be used for a cursor?

The knowledge sources do not explicitly mention

xid8

as a supported cursor type for the Postgres source connector. Based on the documented supported cursor types, only the following field types can be used as cursors: [Supported Cursors] •

TIMESTAMP

,

TIMESTAMP_WITH_TIMEZONE

•

TIME

,

TIME_WITH_TIMEZONE

•

DATE

•

BIT

,

BOOLEAN

•

TINYINT/SMALLINT

,

INTEGER

,

BIGINT

•

FLOAT/DOUBLE

,

REAL

•

NUMERIC/DECIMAL

•

CHAR/NCHAR/NVARCHAR/VARCHAR/LONGVARCHAR

•

BINARY/BLOB

xid8

(a 64-bit transaction ID type in PostgreSQL) is not in this list. The connector would likely reject it with an "Unsupported cursor type" error, as the underlying code throws an

IllegalArgumentException

for any type not in the allowed set. Note that the standard

xmin

system column (which uses the

xid

type) is handled separately via the Xmin replication method — but that is a built-in replication mode, not a user-defined cursor field.

xid8

is a distinct type and is not covered by that mechanism either. If you need incremental sync on a table where

xid8

is the only candidate cursor, your options would be: • Use Full Refresh sync mode instead. • Consider adding a proper cursor column (e.g., a

TIMESTAMP

or

BIGINT

) to your table. • Check the Airbyte GitHub for any recent issues or feature requests related to

xid8

support. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.