Redshift external schemas should be discoverable through db access

[programmerq]

Expected behavior:

When using dbeaver or datagrip, any redshift external schemas should populate normally just like when connecting to the database directly.

Current behavior:

When using dbeaver or datagrip, any redshift external schemas do not show up in the gui.

Bug details:

Access a redshift database through db access using dbeaver or datagrip. When setting up the connection, the gui client has both a redshift and a postgres option. the redshift option doesn't seem to work through db access, and the postgres driver does not do the necessary discover steps to find the external schema.

Queries to the external schema can be done manually if the query is issued directly.

gz#5304

gz#5754

[j-teleport]

If using Redshift driver with DBeaver, the error is,

Error getting JDBC meta data.

[halilduygulu]

In our case, same db works with connection from DBeaver if postgres drived is used. If I try to connect via redshift driver, then we get this error message.

Can't connect ot remote PostgreSQL server
  An I/O error occurred while sending to the backend.
  An I/O error occurred while sending to the backend.
    Illegal UTF-8 sequence: initial byte is 10xxxxxx: 141
    Illegal UTF-8 sequence: initial byte is 10xxxxxx: 141

There is a typo in the message, so it can help to identify where is this coming from. I am assuming teleport is still proxying connection via some sort of postgres protocol instead of redshift, so only postgres client lib works.

[gtaber28]

I am seeing following in Error Log from DBeaver 23.1.2, connecting to Redshift PostgreSQL with Amazon Redshift driver jdbc42-2.1.0.3: