You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Metabase launches a query is executed against the app db to set the "search_path" variable in Postgres. The transaction never leaves the "idle in transaction" state.
To Reproduce
Start Metabase v48.5 or higher
On the application database run:
SELECT pid ,datname ,usename ,application_name ,client_hostname ,client_port ,backend_start ,query_start ,query ,state
FROM pg_stat_activity
WHERE state = 'idle in transaction';
Note that the pid with the "set search_path" query in it never resolves.
@ixipixi is this a neatness issue or was there some particular fallout from this? thinking about the priority here and would like to understand the whole picture
@darksciencebase it's not impacting performance afaik but it creates an inconvenience for customers/sys admins/dbas that are monitoring for hanging transactions. They see a transaction stuck in idle for a long time and go research it to discover it's this every time. They know to ignore it but it's not ideal.
Describe the bug
When Metabase launches a query is executed against the app db to set the "search_path" variable in Postgres. The transaction never leaves the "idle in transaction" state.
To Reproduce
SELECT pid ,datname ,usename ,application_name ,client_hostname ,client_port ,backend_start ,query_start ,query ,state
FROM pg_stat_activity
WHERE state = 'idle in transaction';
Note that the pid with the "set search_path" query in it never resolves.
Expected behavior
The transaction should complete.
Logs
No response
Information about your Metabase installation
Severity
Unclear on if this impacts anything other than leaving a single process hanging since this is already the default setting for this value in Postgres
Additional context
No response
The text was updated successfully, but these errors were encountered: