[ https://issues.apache.org/jira/browse/CALCITE-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707735#comment-16707735 ]
Julian Hyde commented on CALCITE-2713: -------------------------------------- I'd like to do a force-push because I messed up the commit message in https://github.com/apache/calcite/commit/e80934465cee318fd306159489ee3e5c768dcb68. May I proceed? If you'd like to go first, that would be fine, just let me know. > JDBC adapter may generate casts on PostgreSQL for VARCHAR type exceeding max > length > ----------------------------------------------------------------------------------- > > Key: CALCITE-2713 > URL: https://issues.apache.org/jira/browse/CALCITE-2713 > Project: Calcite > Issue Type: Bug > Components: jdbc-adapter > Reporter: Jesus Camacho Rodriguez > Assignee: Jesus Camacho Rodriguez > Priority: Major > Fix For: 1.18.0 > > > Varchar length in PostgreSQL cannot exceed 10485760, however Calcite may > generate a cast with length larger than that number, resulting in an > exception. > {noformat} > org.postgresql.util.PSQLException: ERROR: length for type varchar cannot > exceed 10485760 > {noformat} > From {{htup_details.h}} in postgresql: > {noformat} > * MaxAttrSize is a somewhat arbitrary upper limit on the declared size of > * data fields of char(n) and similar types. It need not have anything > * directly to do with the *actual* upper limit of varlena values, which > * is currently 1Gb (see TOAST structures in postgres.h). I've set it > * at 10Mb which seems like a reasonable number --- tgl 8/6/00. */ > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)