PostgreSQL connector truncates long identifiers silently

[ebyhr]

# schema name
trino> CREATE SCHEMA postgresql.a123456789012345678901234567890123456789012345678901234567890123;
trino> SHOW SCHEMAS IN postgresql;
                             Schema
-----------------------------------------------------------------
 a12345678901234567890123456789012345678901234567890123456789012

# table name
trino> CREATE TABLE postgresql.tpch.a123456789012345678901234567890123456789012345678901234567890123 (c1 int);
trino> SHOW TABLES IN postgresql.tpch;
                              Table
-----------------------------------------------------------------
 a12345678901234567890123456789012345678901234567890123456789012

# column name
trino> CREATE TABLE postgresql.tpch.test (a123456789012345678901234567890123456789012345678901234567890123 int);
trino> DESC postgresql.tpch.test;
                             Column                              |  Type   | Extra | Comment
-----------------------------------------------------------------+---------+-------+---------
 a12345678901234567890123456789012345678901234567890123456789012 | integer |       |

https://www.postgresql.org/docs/current/limits.html

identifier length | 63 bytes | can be increased by recompiling PostgreSQL

I think we should block such identifiers using:

• DatabaseMetaData#getMaxCatalogNameLength
• DatabaseMetaData#getMaxSchemaNameLength
• DatabaseMetaData#getMaxTableNameLength
• DatabaseMetaData#getMaxColumnNameLength

[findepi]

Do you know why PostgreSQL chose to silently truncate identifiers in CREATE SCHEMA / CREATE TABLE?
is there any related PostgreSQL issue about this?

[ebyhr]

@findepi JDBC driver reports the truncation via Statement#getWarnings, so it's not "silent" actually. I couldn't find relevant issues.

[findepi]

well.. warning is too late, as the object is already created. It's created with a different name, so we cannot clean it up, even if we understood the warning and wanted to clean up.

I couldn't find relevant issues.

worth filing?