Anjali Mandowara
05/13/2025, 9:35 AMMoises Morales
05/13/2025, 1:18 PMAnjali Mandowara
05/14/2025, 6:05 AMMoises Morales
05/14/2025, 9:14 AMLakhan Rathore
05/14/2025, 9:21 AMDaniel Stourac
05/14/2025, 12:30 PMLakhan Rathore
05/14/2025, 4:25 PMLakhan Rathore
05/14/2025, 4:26 PMLakhan Rathore
05/16/2025, 5:06 AMDaniel Stourac
05/16/2025, 11:45 AMprepared statement "***" already exists
. This causes the filters to fail. According to internet discussions, this has something to do with connection pooling on Postgres. I couldn't find a clean solution.
2. The two visualizations seem to fail strictly after 30 seconds. The error message in our logs is "Connection is closed"
. Some kind of timeout almost certainly.
If you have access to the Postgres logs, could you please look for messages such as too many clients
or too many connections
? Or, perhaps, anything about timeout
? We don't have visibility there - all we get is that Postgres has closed the connection after 30s. We can only guess about the reasons. Can you check the Postgres logs to help us find the reason, please?Lakhan Rathore
05/19/2025, 7:24 AMDaniel Stourac
05/19/2025, 9:16 AMDaniel Stourac
05/20/2025, 7:11 AMprepared statement "***" already exists
. The latter one is related to PgBouncer and can be solved to switching it from transaction mode
to session mode
. You may have done it already - if not, consider this change to improve stability. We are also preparing some changes in our JDBC driver as a long-term solution.Lakhan Rathore
05/20/2025, 7:12 AM