thswlsqls opened a new issue, #8605: URL: https://github.com/apache/paimon/issues/8605
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ ec1d8ee8a **Compute Engine** Flink (Postgres CDC — postgres_sync_table / postgres_sync_database) **Minimal reproduce step** Sync a Postgres table containing a `numeric(50, 2)` column (Postgres allows precision up to 1000). `PostgresTypeUtils.toDataType()` (paimon-flink-cdc `.../action/cdc/postgres/PostgresTypeUtils.java` line 125-136) passes the JDBC `COLUMN_SIZE` precision straight into `DataTypes.DECIMAL(precision, scale)` with no upper-bound guard. **What doesn't meet your expectations?** Because Paimon `DecimalType.MAX_PRECISION` is 38, `DataTypes.DECIMAL(50, 2)` throws `IllegalArgumentException("Decimal precision must be between 1 and 38")`, so schema derivation fails and the whole CDC sink never starts. The sibling `MySqlTypeUtils.toDataType()` (line 259-261, same `JdbcToPaimonTypeVisitor` SPI) already guards this with `length <= 38 ? DECIMAL : STRING`; Postgres should behave the same and fall back to STRING (ARRAY(STRING) for `_numeric`). **Anything else?** N/A **Are you willing to submit a PR?** - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
