You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trino tries to fetch the columns information of tables, it calls getColumns on DatabaseMetadata of jdbc connector, and for the PostgreSQL JDBC connector, it involves an batch over window, which depends on
Run docker compose up -d to start the demo cluster.
Create a demo table and insert test data via psql client
psql -h localhost -p 4566 -d dev -U root
# within the psql clent
dev=> create table test_table(id bigint);
CREATE_TABLE
dev=> insert into test_table values(1);
INSERT 0 1
dev=> flush;
FLUSH
Query from trino client
docker compose run -it trino-client
# within the trino client
trino:public> show tables;
Table
------------
test_table
(1 row)
trino:public> select * from test_table;
id
----
1
(1 row)
The trino PostgreSQL uses PostgreSQL JDBC connector to access PostgreSQL.
However, when we are currently testing query RisingWave via trino PostgreSQL connector, we gets error when we do select from risingwave table.
The following are some blocking bugs and unsupported features
getTables
with_
in table name: bug: incorrect wildcard handling in LIKE clause compared to pg #10018getColumns
: Unsupported columnatttypmod
in pg internal tablepg_attribute
#10019getColumns
onDatabaseMetadata
of jdbc connector, and for the PostgreSQL JDBC connector, it involves an batch over window, which depends onThe text was updated successfully, but these errors were encountered: