I’m facing a persistent error in Metabase v0.58.5]) where all download/export options (CSV, XLSX, and JSON) fail immediately, even though the query results display perfectly in the dashboard and question editor.
The Error:FATAL: transaction blocks not allowed in statement pooling mode
The Situation:
Database: PostgreSQL.
Infrastructure: The database is managed by an external vendor. I have no access to the server configuration or PgBouncer settings.
Observation: The error occurs only when triggering a download. It appears Metabase/the JDBC driver is attempting to open a transaction block for streaming results, which is prohibited by the provider's statement pooling mode.
Tried & Failed Workarounds: I have already tried to resolve this using additional JDBC connection string options, but none of the following worked:
prepareThreshold=0
reWriteBatchedInserts=true
preparedStatementCacheQueries=0
It seems the issue is not related to prepared statements, but specifically to the fact that Metabase requires an open transaction for cursor-based streaming during exports.
Constraints: Since I cannot change the database-side pooling mode (it's a managed service by a third party), I am looking for a way to make Metabase compatible with this environment.
Questions:
Is there a way to force Metabase to execute exports without wrapping them in a transaction block (e.g., by disabling cursor-based streaming)?
Is there any other JDBC parameter that could potentially bypass the transaction requirement for reads?
Has anyone dealt with a similar "locked-down" DB environment and found a way to enable exports?
Is this Supabase or some sort of cloud database? We recommend connecting directly (IPv4), since the external pooler can conflict with the internal pooling of Metabase, like in this case.
This is a database from the erp system odoo.sh and they seem to block transactions, hence our questions was whether there would be a setting within metabase to avoid transaction pooling.
Given the errors that you sent in your screenshot, I do assume the issue is related to this.
I do suppose that the app acts differently and the one on Mac OS do embed your request into a transaction automatically which close the connection. I can double check with odoo.sh team on the matter, but it is very likely the issue and will take some time. If it is indeed the issue, then you will have to see if the application allow you to disable the PSQL transactions, otherwise, it will not be supported by this odoo.sh feature.”