Feature Request
Please provide a Linux x86_64 (amd64) binary in the release assets.
Use case
I'm running Metabase on a GCP Compute Engine VM (Debian/Ubuntu) and want to connect it to Oracle Fusion via ofpgproxy. Currently, the only way to make this work is:
- Run ofpgproxy on a local Mac (the only platform with a binary)
- Create an SSH reverse tunnel from Mac to GCP VM
- Use
postgres_fdw in PostgreSQL because Metabase's JDBC driver fails on SHOW TRANSACTION ISOLATION LEVEL
This setup works but requires the Mac to be always online, which isn't ideal for production dashboards.
A Linux binary would allow ofpgproxy to run directly on the same VM as Metabase — no tunnel needed, always-on, and much simpler architecture.
Current workaround
Metabase (GCP VM) → PostgreSQL (postgres_fdw) → socat → SSH tunnel → ofpgproxy (Mac) → Oracle Fusion
Desired
Metabase (GCP VM) → ofpgproxy (same VM) → Oracle Fusion
Environment
- GCP Compute Engine, Debian 12 (bookworm), x86_64
- ofpgproxy v0.2.1
- Currently using SSO mode on macOS (local Mac)
- Would use password mode on Linux VM (headless, no Chrome for SSO)
Additional note
While testing, I also noticed that Metabase v0.60.3 (pgJDBC) fails to connect directly to ofpgproxy because SHOW TRANSACTION ISOLATION LEVEL returns an error. I worked around this using postgres_fdw, but native support for this command would also help. Happy to open a separate issue for that if preferred.
Feature Request
Please provide a Linux x86_64 (amd64) binary in the release assets.
Use case
I'm running Metabase on a GCP Compute Engine VM (Debian/Ubuntu) and want to connect it to Oracle Fusion via ofpgproxy. Currently, the only way to make this work is:
postgres_fdwin PostgreSQL because Metabase's JDBC driver fails onSHOW TRANSACTION ISOLATION LEVELThis setup works but requires the Mac to be always online, which isn't ideal for production dashboards.
A Linux binary would allow ofpgproxy to run directly on the same VM as Metabase — no tunnel needed, always-on, and much simpler architecture.
Current workaround
Metabase (GCP VM) → PostgreSQL (postgres_fdw) → socat → SSH tunnel → ofpgproxy (Mac) → Oracle Fusion
Desired
Metabase (GCP VM) → ofpgproxy (same VM) → Oracle Fusion
Environment
Additional note
While testing, I also noticed that Metabase v0.60.3 (pgJDBC) fails to connect directly to ofpgproxy because
SHOW TRANSACTION ISOLATION LEVELreturns an error. I worked around this usingpostgres_fdw, but native support for this command would also help. Happy to open a separate issue for that if preferred.