I have a frontend written in MS Access that connects to a Postgres backend through ODBC. Sometimes the number of sessions reaches 100 and at that point I get an "ODBC call failed" error. I use PG Admin version 6.13 to administer the database. I noticed under Database activity -> sessions the following after some heavy usage on the database:
There are over 70 of these in the session tab, which causes the application to crash. If I close the application, the entries also disappear. Running the SQL returns nothing, as there is no data type with the name "lo" in the table pg_type. The table pg_type is a system table, not one that I created. Any ideas how to fix this excessive number of session entries? And what is this "lo" type?
There are over 70 of these in the session tab, which causes the application to crash. If I close the application, the entries also disappear. Running the SQL returns nothing, as there is no data type with the name "lo" in the table pg_type. The table pg_type is a system table, not one that I created. Any ideas how to fix this excessive number of session entries? And what is this "lo" type?
Asked by Christos Arapidis
(3 rep)
Oct 4, 2022, 08:35 AM
Last activity: Apr 15, 2025, 02:03 AM
Last activity: Apr 15, 2025, 02:03 AM