(DBeaver): Failed connection: Error during planning: Unable to fetch table provider for 'pg_catalog.pg_type'

[greyscaled]

Context

If I try to connect to my GlareDB cloud-hosted db with DBeaver, it gives two options:

• Host
• URL

1. If I try Host with org_name as a subdomain, I get:

FATAL: cloud auth: missing org ID: pass it as an option, or subdomain in proxy or in database as '/'
FATAL: cloud auth: missing org ID: pass it as an option, or subdomain in proxy or in database as '/'

2. If I try Host with org_id as a subdomain, I get:

To me, this indidcates a "successful" connection, minus support for pg_type

ERROR: Error during planning: Unable to fetch table provider for 'pg_catalog.pg_type': Failed to dispatch to table: Missing catalog entry; schema: pg_catalog, name: pg_type
ERROR: Error during planning: Unable to fetch table provider for 'pg_catalog.pg_type': Failed to dispatch to table: Missing catalog entry; schema: pg_catalog, name: pg_type
ERROR: Invalid number of values provided. Expected: 0, got: 1

I get this same response if I set --options in their UI

3. If I try <org_name>/<db_name>, I get:

(under-the-hood, it uses JDBC, and it invalidates URLs that we understand):

Unable to parse URL jdbc:postgresql://proxy.qa.glaredb.com:6543/grey_new/grey_new_db
Unable to parse URL jdbc:postgresql://proxy.qa.glaredb.com:6543/grey_new/grey_new_db

I get a very similar error if I try <org_id>/<db_name>, I get:

Expected

I'm able to connect to GlareDB with DBeaver. It's worth noting JDBC doesn't play nicely with some of our formats, but there are always workarounds. However, given how frequently I've run into this, we may want to consider how we present connection strings down the line.

Actual

I cannot successfully hookup GlareDB isntance with DBeaver

Impact

[greyscaled]

Very similar class of bug to #1445

[YuriyGavrilov]

+1