You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RisingWave doesn't have exactly the same data type as PG. Some PG data types like uuid was converted to RW type varchar. It usually works well when we ingest data from PG.
But in some cases the data stored in RW will be converted to PG type and applied to the PG data source. One example is when backfilling, start_pk_row is originated from PG (e.g. uuid) but converted to RW varchar. When converting the RW varchar back to use as a SQL param, we will get this incorrect binary data format in bind parameter 1
RisingWave doesn't have exactly the same data type as PG. Some PG data types like
uuid
was converted to RW typevarchar
. It usually works well when we ingest data from PG.But in some cases the data stored in RW will be converted to PG type and applied to the PG data source. One example is when backfilling,
start_pk_row
is originated from PG (e.g.uuid
) but converted to RWvarchar
. When converting the RWvarchar
back to use as a SQL param, we will get thisincorrect binary data format in bind parameter 1
risingwave/src/connector/src/source/cdc/external/postgres.rs
Lines 208 to 234 in b5ec2ae
The text was updated successfully, but these errors were encountered: