Jeremy Plummer
11/25/2025, 5:54 PMkapa.ai
11/25/2025, 5:55 PMinvalid input syntax for type double precision: "None" during a destination Postgres sync indicates that Airbyte is attempting to insert the string value "None" into a column of type double precision in Postgres. Postgres expects a numeric value for this type, but "None" is not a valid numeric representation, so it fails with this error. This kind of issue often arises when the source data contains null or missing values, and these are being serialized as the string "None" (possibly from Python or another system) instead of being properly mapped to SQL NULL. When Airbyte's normalization or transformation step tries to cast or insert this value into a numeric column, Postgres rejects it due to the type mismatch. A similar issue is described in the context of normalization errors, where empty strings or incorrect types (like "0.0" for a bigint) cause Postgres to throw input syntax errors for numeric types. The root cause is typically a mismatch between the data type in the source and the expected type in the destination, or improper handling of null/empty values during normalization or transformation steps. Ensuring that nulls are correctly mapped to SQL NULL and that data types are compatible between source and destination should resolve this issue [“invalid input syntax for type” normalization ASP -> Postgres/Mysql](https://discuss.airbyte.io/t/2670)[Invalid Timestamp in basic normalization (source-postgres)](https://discuss.airbyte.io/t/1407). If you are seeing this error, review your source data and normalization logic to ensure that null or missing values are not being converted to the string "None" before being loaded into Postgres.