PostgreSQL interval type columns are decoded as null during backfill (but work correctly in live CDC)

[eladtorq]

When performing a backfill from a PostgreSQL table containing interval type columns, Sequin outputs null for those columns. However, live CDC (WAL-based streaming) works correctly and emits proper interval values.

Expected behavior
Backfill should emit the same interval values as live CDC. Both should produce consistent output.
Impact

Historical data with interval columns cannot be replicated via backfill
Initial sync is incomplete for tables with interval columns
Workarounds require schema changes or manual data migration

Root cause (suspected)
Backfill likely uses SELECT queries to read existing data, while live CDC reads from WAL. The PostgreSQL driver or decoder may handle interval types differently between these two code paths.

Additional context
Live CDC correctly streams interval values from WAL
Issue appears specific to backfill's SELECT-based data reading
Transforms cannot fix the issue as data arrives as null before transform execution
Other PostgreSQL types work correctly in both backfill and live CDC

[adir-torq]

@dosu
I would like to create a PR with the fix for this issue and do not have any permissions (can only fork) - is there an option to open a PR and for someone to approve and merge it?
Thanks!

[jkazimierczak]

@adir-torq seems like a standard contribution flow. Fork, create new branch, do the changes, push to your personal fork, open PR from your personal fork against this repository, and let someone from Sequin team review, and (possibly) merge it.

[acco]

Thanks @adir-torq , @jkazimierczak ! Fixed in e2c0283, release coming later today

Went with behavior that aligns well with Postgres and our db driver (Postgrex):

      {
          "days": 0,
          "microseconds": 1800000000,
          "months": 0
        },