[
https://issues.apache.org/jira/browse/FLINK-36303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956281#comment-17956281
]
Rui Fan edited comment on FLINK-36303 at 6/12/25 8:50 AM:
----------------------------------------------------------
Merged to main(4.1.0) via:
* 319962ca28598de0f23657ed37986597e3eaef9a
* 4d3351e3647bbb73b6c9f35eeeef47f824d06a7f
was (Author: fanrui):
Merged to main(4.1.0) via: 319962ca28598de0f23657ed37986597e3eaef9a
> PostgreSQL timestamp precision 0 not supported
> ----------------------------------------------
>
> Key: FLINK-36303
> URL: https://issues.apache.org/jira/browse/FLINK-36303
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Affects Versions: jdbc-3.2.0
> Reporter: Ken Geis
> Assignee: Ken Geis
> Priority: Minor
> Labels: pull-request-available
> Fix For: jdbc-4.1.0
>
>
> I am having trouble with Flink 3.2.0 recognizing my timestamp(0) columns in
> PostgreSQL 15.
> PostgresDialect code says:
> {code:java}
> // Define MAX/MIN precision of TIMESTAMP type according to PostgreSQL
> docs:
> // https://www.postgresql.org/docs/12/datatype-datetime.html
> private static final int MAX_TIMESTAMP_PRECISION = 6;
> private static final int MIN_TIMESTAMP_PRECISION = 1;
> {code}
> The linked documentation says:
> {quote}{{{}time{}}}, {{{}timestamp{}}}, and {{interval}} accept an optional
> precision value _{{p}}_ which specifies the number of fractional digits
> retained in the seconds field. By default, there is no explicit bound on
> precision. The allowed range of _{{p}}_ is from 0 to 6.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
