Stitch Data cannot connect - detecting CrateDB version instead of Postgres Version

Integrations 3rd Party Tools
1

If I look at the docs Session settings — CrateDB: Reference

it looks like crate does export the Postgres server version as server_version.

However it looks like stitch data is checking another way,
which begs the question, should crate be exposing the Postgres version in SELECT version() or should Stitch change the way it detects the Postgres version?

2022-11-04 10:42:06,471Z   main - INFO Attempting to connect to PostgreSQL destination
2022-11-04 10:42:07,373Z   main - INFO Successfully connected
2022-11-04 10:42:07,373Z   main - INFO Checking database version
2022-11-04 10:42:07,737Z   main - INFO Version: CrateDB 5.1.0 (built 5c9617d/2022-10-11T09:42:10Z, Linux 3.10.0 amd64, OpenJDK 64-Bit Server VM 18.0.2+9)
2022-11-04 10:42:07,737Z   main - CRITICAL Database version check failed
2022-11-04 10:42:07,737Z   main - CRITICAL Error when attempting to execute "SELECT version()"
2022-11-04 10:42:07,737Z   main - CRITICAL Connection attempt failed
2022-11-04 10:42:07,737Z   main - CRITICAL Only PostgreSQL version 9.3 and above is supported
2022-11-04 10:42:07,743Z   main - INFO Exit status is: Check failed with code -1.
2

or maybe should there be a way that can be configured/overridden for compatibility reasons?

3

Checking the postgresql version number via SELECT version() seems to be a rather weird way of doing things, when SHOW server_version; and SHOW server_version_num exists. Changing what version() is non trivial.

The PostgreSQL tap is available GitHub - singer-io/tap-postgres: tap-postgres however, the exceptions don’t seem to match up, whit the logs from stitch, so I don’t know, if they internally use something different.
Seems like Stich is also open to provide custom taps, for their paying customers:
Connecting Other Data Sources to Stitch | Stitch Documentation

4

Thank you, logging the issue with stitch.